Skip to main content
Business & GrowthCustomer Support Services30 lines

Verify Chatwoot Inbox Routing and Handoffs

Configure a Chatwoot test inbox, verify team ownership and conversation handoff, and handle event retries without duplicate actions.

Quick Summary8 lines
Record the Chatwoot version, account, inbox type, team, and users permitted to access it. Use a test inbox and synthetic contacts. Define who should see a new conversation, when it is assigned to a team or individual, and what status should follow resolution. Decide how an unassigned conversation is discovered and who owns that exception.

## Key Points

- [Chatwoot API introduction](https://developers.chatwoot.com/api-reference/introduction)
- [Chatwoot webhook setup](https://developers.chatwoot.com/api-reference/webhooks/add-a-webhook)
skilldb get customer-support-services-skills/chatwootFull skill: 30 lines
Paste into your CLAUDE.md or agent config

Verify Chatwoot Inbox Routing and Handoffs

Map one support handoff

Record the Chatwoot version, account, inbox type, team, and users permitted to access it. Use a test inbox and synthetic contacts. Define who should see a new conversation, when it is assigned to a team or individual, and what status should follow resolution. Decide how an unassigned conversation is discovered and who owns that exception.

Inspect the inbox identity and verify which channel or integration supplies messages. Record whether the task uses an account-level API or a channel-facing interface and use the documented credential for that scope. Keep inbox and account identifiers separate. Avoid storing message contents or contact details in generic diagnostic logs. Use a fixture conversation whose title and timestamps make it distinguishable from live tickets.

Verify events and user visibility

Exercise a controlled handoff and inspect conversation state in the intended view or API. Collect assignment evidence by recording the conversation ID, current inbox, team or agent, and relevant timestamps. Check whether permitted staff see exactly the expected information. Test a user outside the inbox or team where the product's access policy applies. A successful admin test cannot establish what ordinary agents can see.

If webhooks are in scope, check supported event names and the installed version's documented authentication or delivery protections. Verify incoming events before acting. Implement event deduplication using a stable event identity or a documented local fingerprint. Keep irreversible actions separate so a retry cannot reassign an old ticket or send a duplicate reply. When event ordering is uncertain, reconcile current conversation state before writing.

Rehearse a routing failure

Test a new conversation, an unavailable assignee, an unsupported event and repeat delivery. Confirm that the conversation remains visible to the intended team or reaches a known exception path. Validate the final status and assignment after the workflow completes. Do not infer state solely from a notification.

Keep the inbox settings, routing rules, role expectations, API identifiers and outcomes with the staging record. If a webhook test could only use a fixture, record that real provider delivery and permissions still need validation. Leave real conversation changes or outbound messages behind the existing support authorization process.

References

Install this skill directly: skilldb add customer-support-services-skills

Get CLI access →