Custom integrations,
not an app store.
Every call, message, fax, recording and contact through one REST API. Eleven webhook events. Built-in helpers that need no code. Your developer or a no-code tool connects what you use. Included in every seat.
Not an app store. An open platform.
Most phone-system companies hand you a marketplace of pre-built tiles and wish you luck. What you actually need is not on the list, the API sits on a higher tier, and the local reseller has no API at all.
We took the other road. Calls, messages, faxes, recordings, contacts and your AI agents are on one REST API, in every seat. Names and record links need no code. Anything else is a small job for your developer or a no-code tool, with docs a person wrote and a person who answers when you ask.
Pick the road that fits. Or all three.
Nothing here is an add-on. The helpers, the webhooks and the API are part of every seat.
Names and record links
Get your customer names onto every call with no code at all. Upload a contact list, or email one in to your company’s own import address. From then on Callpop, Reports and your desk phones show the name, and one click opens the record in your own system.
- Contact directory: upload, email import, or the API
- Record links: a URL pattern per system, one click from Callpop
- Works with QuickBooks, Salesforce, HubSpot, Zoho, HHAeXchange, or any URL
Webhooks and no-code tools
Eleven event types pushed to your endpoint, each signed with HMAC-SHA256 so you can prove it came from us. Call and message events arrive within seconds, fax events within a minute, and the transcript event once the summary is ready.
- call.started, call.answered, call.ended, call.transcription
- message.sent, message.received, message.status_updated
- fax.sent, fax.received, fax.delivered, fax.failed
The REST API
Every call with its full journey, summary and transcript. Every text and WhatsApp message, and sending texts. Faxes, recordings, attachments, contacts and your AI agents. A main key from your own Integrations page, scoped to your data.
- Calls, messages, faxes, media, contacts, callers, AI agents, webhooks, support
- 500 records a page, dates default to today in Eastern time
- 20 texts a minute and 200 a day on the main key; a metered texting key for volume
How the three kinds
of phone company handle it.
The big-brand app store
- A fixed list of pre-built connectors
- You adapt to their integration
- The API sits on a higher tier
- Not on the list? You are stuck
The local reseller
- Maybe three or four CRMs supported
- One-size-fits-all implementation
- Custom work is not on the menu
- No API at all
Vocatech
- Names and record links, no code
- API and webhooks in every seat
- No-code tools or your developer
- Signed, rate-limited, supported
Four products,
one set of data.
Whatever you connect flows through the products your team already uses. The coordinator sees the right record in Callpop. The summary shows up in your CRM. Nobody has to know the plumbing is yours.
What customers
connect, and how.
Every example below runs on the roads above. A small job for a developer, less in a no-code tool.
Auto-log every call in your CRM
Subscribe to call.ended and call.transcription. When the summary lands, your script or a Zapier zap creates the activity on the matching contact with the summary, the transcript and the duration.
Balance due, on the popup
Sync your accounting contacts into the directory with a record link. When a customer calls, Callpop shows who they are, and one click opens their account in QuickBooks before you say hello.
Appointment reminders by text
Your scheduling system calls POST /v1/messages the day before each visit, from your own business number. Replies land in the same Textdock space your team already watches, so nothing is missed.
Patient match for a homecare agency
HHAeXchange or your EHR exports the caregiver and patient list to the directory. The coordinator sees who is calling, and which case, before picking up, and one click opens the chart.
A support ticket from your own system
A help desk sync or an automation step posts to /v1/support/tickets from your own software. The ticket belongs to your account and lands in our inbox the way a call or an email would.
Your in-house tool
Custom dispatch software, an internal ERP, proprietary case management. If it has an API, your developer or a no-code tool wires it to ours with the same keys and webhooks. Nothing extra to buy.
Four steps. No ticket.
The API reads and sends.
It does not change call settings.
Forwarding, voicemail, Do Not Disturb and the rest live in the portal, where a change is live the moment you save. If you need something the API does not do yet, tell us. We read every request.
One service. Seven products. Every feature your team expects.
Everything on this page is part of the same Vocatech service. Nothing on it is an upgrade tier. Nothing on it is a premium add-on.
Connect what
you already use.
Read the docs, generate a key, and ask us anything along the way. A person answers, and yes, they have read the API.