Voca for support — onboard, escalate, and educate from a tap.
When a customer needs help on-site, the last thing they want is a printed FAQ. Voca turns your tech's card into a self-serve dispatcher — visitors pick what they need, the right resource opens immediately, and your CSAT score goes up because nobody waits on hold.
The problem
- Field techs leave behind business cards with a 1-800 number — customers call when the queue is at 40 minutes.
- Onboarding new customers means emailing a 14-link checklist; half of them never open it.
- Different issues need different escalation paths — billing vs technical vs renewal — but support cards are one-size-fits-all.
The workflow
-
1
Customer taps the card
Left by a field tech, attached to a product, or printed in onboarding material — any NFC or QR tap opens the Voca profile.
-
2
Pick the issue
Intent chips: Billing question · Setup help · Bug report · Just exploring. Each one rewrites the recommended action.
-
3
Resolve or escalate
Billing → Stripe portal link. Setup → 3-minute Loom + WhatsApp the tech. Bug → file a ticket with the product+serial pre-filled.
-
4
Loop closure
(Pro) The tap webhook posts to Slack / Zendesk; the assigned engineer gets paged with full context. No phone-tag.
Why it works
-
Deflect routine tickets
Common-issue self-serve links handle 30-50% of taps without an agent.
-
Faster first response
Customer reaches the right channel in one tap instead of hold-music limbo.
-
Per-tech attribution
Each engineer's card surfaces their own Calendly + WhatsApp, so warm relationships persist.
Field technician template
A copyable starting point. Edit anything in the dashboard.
| Name + role | Priya Singh · Senior Service Engineer |
| Primary action | Book a follow-up visit |
| Secondary | WhatsApp me · Loom: First Setup · KB: Common Issues |
| Intent chips | Setup · Bug · Billing · Renewal |
| Webhook | POST → zendesk.com/tickets |
FAQ
Can different products have different default cards?
Yes — give each product line its own Voca handle and the on-product NFC chip points there.
Does it integrate with Zendesk / Intercom?
Via the CRM webhook on Pro. The payload includes intent + selected CTA, which most help-desk tools accept as ticket metadata.
What if there's no internet at the customer site?
The Apple Wallet pass keeps the contact info offline. The web tap requires data — same as visiting any web page.
Can customers see the engineer's calendar?
Only the available slots they expose via Cal.com / Google Calendar — Voca is just the routing layer.
Related use cases
Same product, different playbook.
Ready to set yours up?
Cut onboarding from days to one tap.