Vocatech
Contact

Platform · Integrations

Custom integrations, not an app store.

Every call, text, fax, recording and contact on one REST API, eleven signed webhook events, and a contact directory that needs no code. Your developer or a no-code tool uses the same API we use. Included in every seat.

Contact Developer docs
Included in every seat
What it does

Eight things, all of them included.

Nothing here is an add-on. The contact directory, webhooks and API are in every seat, and the API is the one we use ourselves.

The contact directory

Your contacts with the columns you define, uploaded, emailed to your import address, synced on a schedule or sent by the API.

Record links

An address per system filled from the contact’s fields, so Callpop opens the record in your own system with one click.

The REST API

Every call with its journey, summary and transcript, every text and fax, your contacts and your agents, from one key.

Webhooks

Eleven signed events pushed to your address. A call starts, ends, gets its transcript. A message or a fax lands.

Texting by API

Send a text or a picture message from your own number through the API, and the replies land in the space your team watches.

Faxing by API

Send a PDF as a fax through the API and read the list of faxes sent and received, with a signed link to each.

The AI Agent

The agent asks your system during a call and files what it took, and the API can have it place an outgoing call.

Support by API

Open a ticket in our inbox from your own system through the API, and ask our knowledge base a question the same way.

The ways in

Five screens, from no code to your developer.

The reference and the guide as they render, a call as the API returns it, a signed webhook, the contact directory and the key, each a real page.

The reference

Every endpoint, documented.

The API reference on vocatech.com, every route with its fields, answers and examples.

  • Calls, messages, faxes, media, callers, contacts, agents and webhooks.
  • JSON over https, server to server, one key in the header.
  • A plain-English guide beside it, with a recipe for each job.
  • Scopes that narrow a key to messaging, agents, support or knowledge.
A call

A call, as the API returns it.

One request for today’s calls, and each call comes with everything Reports knows about it.

  • Every leg of the journey, the menu, the group and the person, in order.
  • The AI summary and the transcript, once they are ready.
  • A signed link to the recording, good for thirty minutes.
  • Up to a year a request, five hundred calls a page.
Webhooks

Pushed to you, the moment it happens.

Eleven events, each delivery signed, so your server never has to ask.

  • A call starts, is answered, ends, and gets its transcript.
  • A message is sent, received, or changes status. A fax, the same.
  • Signed with your secret, and tried five times when your server is down.
  • Filtered by event, by extension or by number, up to two hundred.
Contacts

Your names on every call, with no code.

The contact directory, with the columns you define, fed four ways.

  • Uploaded, emailed in, synced on a schedule, or sent by the API.
  • A column is a phone to match on, a field to show, or a key for a record link.
  • The same rows name callers in Callpop, Reports and the AI Agent.
  • Pushed to the desk phones’ directory every hour.
The key

One key, locked to your addresses.

Made on your Integrations page in the portal, by a login that may edit the company.

  • Shown, copied or regenerated there. Nothing is emailed.
  • Locked to exact addresses, or open to any until you lock it.
  • Every attempt logged for two weeks, the rejected ones at once.
  • Every read of calls, texts and recordings written to your access log.
What offices connect

The same API, a different system in every office.

Every one of these is built from the pieces above, a small job for a developer and less in a no-code tool.

Retail

The order on the call

The store’s customers sync into the directory with a link to the order, Callpop opens it before hello, and the AI Agent reads the order system during a call and files the pickup it took.

Home care

The caseworker on the popup

The agency’s system exports the client and the aide on the case to the directory every hour, so the coordinator sees who is calling and which case, and one click opens the chart.

Healthcare

The reminder, by text

The scheduler sends the day-before reminder from the practice’s own number through the API, and the replies land where the desk already answers, with no patient detail in them.

Real estate

The ticket from the call

The tenant’s record link opens the building’s file, and when the AI Agent takes a maintenance request, a webhook fires and the office’s own ticket system opens the ticket with the summary.

Accounting

The balance due, before hello

The firm’s accounting contacts sync into the directory with the open balance as a field, so the popup shows it when the client calls, and every call lands in the firm’s own records by webhook.

Insurance

Every call in the claim

The claim system subscribes to the end of a call and to its transcript, and when the summary lands, the activity is written on the matching claim with the summary and the recording link.

Why it is different

Not an app store. An open platform.

Most phone systems hand you a marketplace of pre-built connectors and wish you luck. What you need is not on the list, and the API sits on a higher tier.

The usual way

An app store of tiles.

  • A fixed list of pre-built connectors.
  • You adapt your work to their integration.
  • The API sits on a higher tier, if there is one.
  • A connector that breaks when the vendor changes.
  • Not on the list? You are stuck.
The Vocatech way

The same API we use, in every seat.

  • Names and record links with no code at all.
  • The API and the webhooks in every seat.
  • Your developer or a no-code tool, your choice.
  • Every attempt logged, and every read in your access log.
  • Signed, documented, and a person who answers.
How it starts

Three steps, and your records are on the call.

The contact directory takes an afternoon with us. The API takes your developer a morning with the guide, and we read every request for what it does not do yet.

  1. 01

    Put your contacts in

    Upload a list or email one to your import address, mark the columns to match and to show, and the names are on every call. We set it up with you.

  2. 02

    Generate a key

    On your Integrations page in the portal, by a login that may edit the company. Lock it to your addresses, and nothing is emailed.

  3. 03

    Subscribe and build

    Create a webhook with the events you want, read the guide, and connect your tool or your script. A person answers, and they have read the API.

Straight answers

What offices ask about integrations first.

“Do you build the integration for us?”

Names and record links need no code at all, and we set them up with you. For your own software we connect to what you run when it has a standard API, and we take on custom work when it needs it. Ask us, and a person answers.

“Which systems work with it?”

Any system with an address that takes an id gets a record link in Callpop. Any system with an API can be read by the AI Agent or fed by webhooks. QuickBooks, Salesforce, HubSpot, Zoho and HHAeXchange are in use today.

“Is there a limit on calls to the API?”

Yes, a generous one for an office, counted per key by the minute, the hour and the day, and the reference lists every counter. Texting from the main key includes an allowance, and a metered key carries the volume past it.

“Can the API change our phone settings?”

No. It reads and sends. Forwarding, voicemail, menus and the rest live in the portal, where a change is live the moment you save, and the API creates no logins. If you need something it does not do yet, tell us.

“Is our data safe in it?”

A key is scoped to your account and can be locked to your addresses. Every attempt with it is logged for two weeks, and every read of calls, texts, faxes and recordings is written to your account’s access log, kept six years.

“Which events can we subscribe to?”

Eleven. A call starts, is answered, ends and gets its transcript. A message is sent, received or changes status. A fax is sent, received, delivered or fails. Anything else is refused when the subscription is made.

“How fast is a webhook, and what if we are down?”

Within seconds of the event, the transcript one when the summary is ready. Your server answers within five seconds. A failed delivery is tried five times over about three hours and stays listed for seven days, with no replay after.

“Can the API send WhatsApp?”

No. It sends texts and picture messages from your own number, up to 1,600 characters, with a dry run that checks everything and sends nothing. WhatsApp is answered from the Webex space, the Messaging page or email.

“Is there a way in for an AI assistant?”

Yes. A coding assistant reads the developer guide in plain text and the OpenAPI file, and Ask AI inside the portal answers plain questions about your account on its own. The AI page says how.

“Does it cost extra?”

No. The contact directory, the webhooks and the API are part of every seat, with nothing to license and no tier. Only texting past the included allowance is metered, per message, through a key of its own, and the pricing page says how.

One service, eight parts. Everything on this page runs on the same phone system, is set in the same portal, and lands in the same Reports.

See the whole platform
ReportsCallpopTextdockAI AgentAppsPortalIntegrationsFaxing

Included in every seat

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.

$29.95 per seat per month, every feature in every seat, month to month, no contract. Add-ons and usage

Contact Read the help guide