Delivery failures

When InboxAgent tries to create a lead or ticket and your CRM or helpdesk returns an error, the failed push lands on Advanced → Delivery failures (admins only) with everything you need to understand it.

What you’ll see

Each failure shows which system (Zoho CRM, Zoho Desk, or HubSpot), the operation (e.g. Create Lead), the exact error message, and when it happened. Click View for the detail: the full error, a link to the related email in the logs, and the payload — the exact data InboxAgent tried to send, useful when a validation rule on the other side is the culprit.

What the buttons do — and don’t do

Mark resolved and Ignore are acknowledgements: they clear the entry from the open list so the screen reflects reality. Neither re-sends anything. Nothing is pushed to your CRM by acting here.

To actually get the email across after fixing the cause:

• Open the email in Inbox activity and Re-classify it to Create a lead / Create a ticket — duplicate-safe, so it’s harmless if a record partially exists.
• Or, if the email is in Manual review, resolve it there.

Common causes, quick fixes

• Connection expired / revoked — the bell shows an integration alert; click Connect on that system’s card to reconnect (Zoho CRM, Zoho Desk, HubSpot).
• No default department (Zoho Desk only) — set it on the Zoho Desk card; tickets can’t be created without one.
• A validation rule or plan limit on the other side (a mandatory field, a cap on your plan) — the payload view shows exactly what was sent, so you can see which field tripped it and adjust the rule there.

Note the boundary with what-if-no-integration: “nothing is connected at all” is recorded on the email itself in System logs — this screen is for a connected system that then failed, whether it returned an error or the connection is misconfigured (like a missing Desk department). Both raise alerts so you hear about it either way.