No invoice number?
No problem.
Customers rarely have their invoice handy. So we built the flow around what they actually have — a phone number, a name, an old service ticket. Anything that lets us find the order.
Compare the actual conversation flows.
Dead-end loop
Composite illustration of the typical failure mode
Resolved
Same scenario, after
Six things that end the loop.
Phone-first lookup
Customer types a phone — we find the order. Most know their phone; few know their invoice.
Claim → invoice resolver
If they give an old service ticket number, we resolve it to the original invoice transparently — no dead-end.
Phone verification escape
The phone on a 2021 invoice may not be the customer's phone today. After two tries we offer phone-first lookup — same number, different mechanism.
Empathy in failure modes
"That phone might be different from your current number — try a spouse's, or an older one." Specific suggestions, not blame, not a robot loop.
Auto work-order creation
The platform files the claim directly with your service system. Conversation transcript attached as a PDF. Reference numbers returned in a recap card.
Page-aware shortcut
If the customer is on a product page, we confirm the page product first ("Looks like you're on the [Product] page — is that what you need help with?") and skip the lookup entirely if yes.
Customers don't memorize invoice numbers.
We don't ask them to.
Phone, claim number, invoice, page context — any of them works. Same flow, different starting point. No dead-end loops, no blame, no "please call us during business hours."