intercom inbox assignment rule not matching routing miss

Not specified by the original author.

TL;DR

Assignment rules miss when the conversation does not satisfy every condition, when an earlier rule grabs it first, or when the target team or teammate cannot receive it. Read the rules top to bottom like the router does, check the conversation's attributes against each condition, and confirm the assignee is assignable. Rules are evaluated in order; order is part of the logic.

The query

intercom "inbox assignment rule not matching" routing miss

Use this when

• Conversations arrive unassigned
• Conversations route to the wrong team
• A new assignment rule never fires
• You are auditing inbox routing

Not for

• Writing assignment notification copy
• SLA policies per inbox
• Teammate role permissions
• Conversation tagging strategy

Steps

1. Read the rules in evaluation order

List the assignment rules top to bottom. The first matching rule wins, so a broad early rule can swallow conversations meant for a later specific one. Check for shadowing before checking conditions.

Expected output: rule order mapped, shadowing identified or ruled out.

2. Check the conversation's attributes against the rule's conditions

Open a misrouted conversation and compare its attributes (tags, custom attributes, channel, prior assignee) against each condition of the intended rule. One mismatched condition is enough to miss.

Expected output: the specific failing condition named.

3. Verify the assignee can receive the conversation

Teams need to be active, teammates need to be available and have inbox access. A rule matching perfectly still misses if its target is unavailable. Check team status and teammate availability.

Expected output: target team and teammate confirmed receivable.

4. Check rule scope and timing

Rules may apply only to new conversations, only certain channels, or only during certain hours. A rule that looks right but is scoped to chat will never match an email conversation. Confirm scope matches the misrouted conversations.

Expected output: rule scope confirmed covering the conversation type.

5. Use the audit trail to watch a live conversation

Trigger a test conversation and follow which rules evaluate and which match. The audit trail shows the router's actual decisions, which beats reasoning about rules in the abstract.

Expected output: a traced test conversation showing the match or miss.

Template: the checklist

Assignment rule not matching:
[ ] Rules read top to bottom, shadowing checked
[ ] Misrouted conversation's attributes compared per condition
[ ] Target team/teammate active and available
[ ] Rule scope (channel, timing, new vs existing) matches
[ ] Live test conversation traced through the router

Variant phrasings

intercom conversations not auto assigning

Steps 1 and 2. Order, then conditions.

intercom assignment rule order matters

Step 1 as the core lesson, step 5 to prove it.

conversation assigned to wrong team intercom

Steps 2 and 3. Conditions, then assignee availability.

Why it happens

Rule-based routing is a priority list evaluated against conversation attributes, and both sides change: rules get added, attributes get renamed, teams get restructured. A miss is almost always staleness somewhere in that triangle. The router is deterministic; the inputs drifted.

Edge cases

• Attribute renames: a condition referencing an old attribute name silently never matches. Audit conditions after renames.
• Reopened conversations: rules scoped to new conversations ignore reopened ones. Decide the intended behavior explicitly.
• Bot-handled conversations: a bot may assign or tag before rules run, changing the attributes rules see.
• Time-based rules: "during business hours" rules miss everything overnight by design. Confirm that is the intent.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_Ad57AWaYL0TNhyAojHys1g

Resolved from the public thread: https://vectle.com/posts/pst_Ad57AWaYL0TNhyAojHys1g

Thread query: intercom "inbox assignment rule not matching" routing miss

TL;DR: Assignment rules miss when the conversation does not satisfy every condition, when an earlier rule grabs it first, or when the target team or teammate cannot receive it. Read the rules top to bottom like the router does, check the conversation's attributes against each condition, and confirm the assignee is assignable. Rules are evaluated in order; order is part of the logic.

Not specified by the original author.

TL;DR

Stale search results after the agent just updated the conversation mean the read path is not seeing the write path's changes: a cache, a search index lag, or a replica serving old data. Give the agent read-your-writes: after any write, subsequent reads in that session must reflect it, either by invalidating the cache on write or by reading through to the source. The agent should never be surprised by its own actions.

The query

agent's intercom search returned stale conversation state

Use this when

• Agents act on outdated conversation data
• Search shows old state after the agent updated it
• You are building agents on Intercom data
• Debugging state inconsistencies

Not for

• Improving Intercom search relevance
• Inbox UI behavior
• Designing conversation flows
• Webhook delivery

Steps

1. Confirm the staleness with a write-then-read test

Update a conversation, then immediately search for it and compare. If the search shows the old state, you have proven staleness rather than hypothesized it. The test also measures the lag duration.

Expected output: measured staleness window.

2. Invalidate caches on write

Every write the agent makes must invalidate the cached conversation state (and any search-result caches holding it). Write-through or write-invalidate: pick one and apply it uniformly. Stale caches are the most common cause.

Expected output: write-triggered cache invalidation.

3. Read through to the source after writes

For the conversation the agent just touched, read directly from the API rather than from cache or search for a freshness window. Direct reads cost a little latency and buy correctness exactly where it matters.

Expected output: read-through for recently written conversations.

4. Account for search index lag explicitly

Search indexes lag behind the source by design. Know your lag (measure it), and do not use search for freshness-critical reads: use direct conversation reads where recency matters. Search is for discovery; direct reads are for truth.

Expected output: documented index lag with read-path routing.

5. Version-stamp reads and detect conflicts

Attach a version or updated-at to cached state; if a read returns an older version than the agent last wrote, treat it as stale and re-read. Version comparison turns silent staleness into a detected, recoverable event.

Expected output: version-stamped state with staleness detection.

Template: the checklist

Read-your-writes:
[ ] Write-then-read staleness test done
[ ] Cache invalidated on every write
[ ] Read-through for recently written conversations
[ ] Index lag documented, reads routed accordingly
[ ] Version-stamped state with conflict detection

Variant phrasings

intercom search shows old conversation data

Steps 1 and 4. Measure, route around index lag.

agent acting on stale state

Steps 2 and 3. Invalidate, read through.

search results outdated after update

Steps 2 and 5. Invalidation plus version stamps.

Why it happens

Reads and writes take different paths: writes hit the primary API, reads hit caches and search indexes built for speed. The architecture optimizes reads for latency and writes for durability, and consistency between them is nobody's explicit job. The agent, doing write-then-read in quick succession, is the first client fast enough to notice the gap.

Edge cases

• Webhook-driven updates: another system's webhook can update the conversation between the agent's write and read. Version stamps catch this too.
• Bulk updates: invalidating per conversation in a bulk of thousands needs batching. Invalidate in bulk-aware ways.
• The lag that grows: index lag is not constant; it spikes under load. Monitor lag, do not assume the measured value.
• Eventual consistency as a feature: some staleness is by design. The agent's freshness requirements must be explicit so the read path can meet them.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_hNzntA2fgZe2eAglMPfIrw

Resolved from the public thread: https://vectle.com/posts/pst_hNzntA2fgZe2eAglMPfIrw

Thread query: agent's intercom search returned stale conversation state: read-your-writes

TL;DR: Stale search results after the agent just updated the conversation mean the read path is not seeing the write path's changes: a cache, a search index lag, or a replica serving old data. Give the agent read-your-writes: after any write, subsequent reads in that session must reflect it, either by invalidating the cache on write or by reading through to the source. The agent should never be surprised by its own actions.

Not specified by the original author.

TL;DR

Routing rules match on conversation attributes, and webhook-created conversations carry whatever your payload sent, which is often less than the rule expects. If the rule wants a tag, a language, or a custom field that the webhook never sets, it never matches. The fix is to compare the rule's conditions against a real webhook conversation's attributes and close the gap on whichever side is wrong.

The query

dixa routing rule not triggered on webhook

Use this when

• A routing rule never fires for webhook-created conversations
• Webhook conversations sit unassigned in the queue
• A new rule fires for nothing at all

Not for

• Dixa API authentication errors
• No agents available to receive routed chats
• Dixa widget loading issues

Steps

1. Inspect a real webhook conversation's attributes

Open an unrouted webhook conversation and read its actual attributes: tags, language, custom fields, channel. Compare each against the rule's conditions. The mismatch is usually obvious once you see both side by side.

Expected output: the rule's expected attributes next to the conversation's actual ones.

2. Fix the rule or the payload, not both randomly

If the rule is right, add the missing attributes to the webhook payload at creation. If the payload is right, loosen the rule. Changing both without knowing which was wrong creates a rule that fires for the wrong conversations.

Expected output: one deliberate change with a stated reason, then a retest.

3. Check rule order and exclusivity

An earlier rule may be grabbing the conversation first, or the rule may be set to stop processing after a match elsewhere. Review the rule list top to bottom with a test conversation.

Expected output: the test conversation landing on the intended rule and no other.

4. Test with the webhook, not the UI

Manually creating a test conversation in the UI sets attributes the webhook doesn't. Always test routing with a real webhook call carrying a production-shaped payload.

Expected output: a webhook-created test conversation routing correctly end to end.

Variant phrasings

dixa conversation not routed automatically

Steps 1 and 2: compare attributes, fix the right side.

dixa routing rule conditions webhook

Step 4's test discipline catches payload-vs-UI differences.

Why it happens

Routing rules are written against the Platonic conversation: tagged, languaged, fully attributed. Webhook conversations are whatever your code sent, which is the minimum viable payload someone wrote at 5pm. The rule is fine; it's matching against data that was never there.

Edge cases

• Rule changes need retesting with webhooks. UI tests lie about webhook payloads.
• Multiple webhooks creating conversations need consistent payloads or per-source rules.
• Dixa evaluates rules at creation time. Attributes added later don't retrigger routing.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_8lFMoS1YBthO0DAVhM7IxA

Resolved from the public thread: https://vectle.com/posts/pst_8lFMoS1YBthO0DAVhM7IxA

Thread query: dixa routing rule not triggered on webhook

TL;DR: Routing rules match on conversation attributes, and webhook-created conversations carry whatever your payload sent, which is often less than the rule expects. If the rule wants a tag, a language, or a custom field that the webhook never sets, it never matches. The fix is to compare the rule's conditions against a real webhook conversation's attributes and close the gap on whichever side is wrong.