Skip to main content

Outbound calling

The Voice module on a business's Status page holds three registrations that change how your outbound calls are treated by the networks carrying them. They are independent of texting, independent of each other, and every one of them needs the same single prerequisite: an approved business.

Start with what none of them do: they are not permission to make calls. Your calls go out either way. What these change is whether the network can prove the call is really from you, whether analytics providers label it, and what appears on the screen.

The three items

Verify calls

Signs your outbound calls so carriers can confirm they genuinely originate from you and have not been spoofed. This is the industry's answer to caller-ID forgery: a signed call carries proof of who put it on the network, and receiving carriers trust the number accordingly.

What it needs from you: nothing but the approved business. There are no fields — expanding the row gives you a single submit control.

What it does not do: it does not put your business name on the screen, and it does not by itself stop a "Spam Likely" label. Those are the other two items. Signing establishes that the call is authentic, not that it is wanted.

This is the one to set up first. It is the cheapest in effort and it underpins how seriously the other signals are taken.

Protect against spam labels

Registers who you are and what your calling looks like with the carriers and analytics providers that decide whether a call gets flagged. Those providers watch calling patterns and, absent any information, treat an unknown business making a lot of calls as a telemarketer.

What it needs from you:

FieldWhy it is asked
Use caseA short label for the kind of calling you do — "Telehealth", for example.
EmployeesRough size of the business. Analytics providers read volume in proportion to size; a small practice making a plausible number of calls looks very different from the same volume with no organization behind it.
Calls per business dayYour typical outbound volume. This is the number a pattern gets compared against, so give a real figure rather than an aspirational one.
Notes (optional)Room to describe the calling precisely. Worth using.

Describe the calls in terms of what they do, for whom: appointment scheduling, reminders and care coordination, placed by the registered organization to its existing patients. That is a pattern a reviewer can recognize and an analytics provider can model. A description written around the technology rather than the purpose tells them nothing they can act on, and volume with no explanation is exactly the shape that gets flagged.

What it does not do: it is not a guarantee that no call is ever labelled. It is registration — it puts real information in front of the systems making the judgement, instead of leaving them to guess. Calling patterns that genuinely look like nuisance calling will still be treated as nuisance calling.

Show your business name

Puts your business name on the recipient's caller ID for outbound calls, on US long-code numbers.

What it needs from you: one field, Caller ID display name, with strict limits:

  • Up to 15 characters — this is a hard limit from the databases that carry it, not a style preference.
  • Must start with a letter.
  • Unaccented letters (A–Z), numbers, periods, commas and spaces only. Everything else is rejected, and the ones that catch practices out are apostrophes, hyphens and ampersands — St. Mary's, Mid-City Clinic and Smith & Jones all need respelling (St Marys, Mid City Clinic, Smith and Jones). Accented letters go too, so "Café Médical" needs an unaccented spelling.

Fifteen characters go fast. Choose something a patient will recognize on a screen rather than the full legal name: the practice name usually beats the entity name. Whatever you pick should be identifiably the business the person expects to hear from — a name they do not recognize is worse than a bare number, because it reads as a stranger who knows their number.

Once submitted, the row shows the name it will display as. Changing an approved name requires re-vetting, so it is worth a minute of thought before submitting.

What it does not do: displaying a name does not make the call trusted or unlabelled. A named call that is not signed and not registered can still be flagged.

Filling forms before you are verified

Every one of these setup forms opens for typing whether or not the business is verified yet. Only the submit control waits on the approved business, and when it does, the row says so: "Verify this business before setting up outbound calling."

That is deliberate. Fill in the display name you want and the volumes you know today, and save. Saving is the request — you do not come back on approval day to press a second button. The item shows "Will submit automatically" and goes in by itself once verification clears. Nothing here is hidden behind a prerequisite — hiding the form was what used to turn a short task into a long one.

Reading the statuses

Each item carries its own status, because each is a separate submission:

StatusMeaning
Not set upNever submitted.
SavedFilled in and saved. Also what a queued item shows once the business is verified — see below.
Will submit automaticallyQueued, and still waiting on business verification.
In reviewSubmitted; being vetted.
ApprovedLive.
Needs attentionRejected or flagged.

"Will submit automatically" only appears while the business is still unverified. It is the reassurance that the wait is ours, not yours. Once verification clears, a queued item reads Saved again until it actually goes in — so Saved does not mean "you still have to do something". Saving was the request either way; nothing waits on you, provided the item's fields are complete. Save takes whatever is typed, finished or not, so an item left half-filled will sit queued instead of going in — if something has waited a long time, open it and check for an empty field.

There is no shared "voice is done" state, and none of these waits on another. It is perfectly normal to have calls verified and approved, spam-label protection in review, and caller name never requested at all.

The app does not show an estimated review time for these. Watch the item's own status rather than counting days — and use the refresh control in the module header to re-read the current state from the provider. Refreshing also picks up items that were set up outside the app.

When something needs attention

Once an item has been submitted, the app no longer offers its setup form — records that have been vetted cannot simply be edited in place. If an item comes back Needs attention, or an approved name has to change, contact support; it has to be removed and recreated rather than amended.

Tips

  1. Set up Verify calls first. It is one click and it is the foundation the other signals are read against.
  2. Give honest volumes. An understated call count that your real traffic exceeds is worse than an accurate one.
  3. Draft the 15-character display name before you open the form — it takes longer to choose than to type.
  4. If a status looks stale, refresh the module before concluding anything is wrong.