Skip to content
Resources

Learn the thing before you buy the tool

Most of what makes automated customer messaging work (or fail) is not the software. These cover the rest.

Where to start, by what you are actually doing

Four collections is three too many if you only have twenty minutes. Pick the row that matches you and ignore the rest.

Working out whether this kind of software is worth it
Start with how to evaluate an AI receptionist, which is written to be argued with rather than agreed with, then what one costs and what the price usually hides. If you are comparing us to a chatbot on your website, that difference is the one that decides whether any of this helps.
About to set it up
The setup guide is the only document here that is generated from the product rather than written about it, so it cannot drift from what the screens actually do. Read it in order, and read the section naming what is not built before you plan around something that is not there.
Stuck on texting rules, which is where most people get stuck
Read the three in the order below. They are a chain rather than a menu: skipping the first makes the second pointless, because a number the carriers have not approved does not deliver whatever your consent wording says.
Already running it and something is behaving oddly
What your AI should refuse to answer covers the commonest surprise, which is an agent declining something you expected it to handle. The glossary is for the moment a carrier error code or a piece of jargon turns up in a screen and means nothing to you.

The one reading order that matters

US business texting has a sequence, and doing it out of order is the single most common way a launch stalls. This is it, and it is four things rather than forty.

  1. 1

    Choose the number

    Local, toll-free, or the one you already use for calls. This decides what registration you need and how long it takes, so it comes first and nothing else is worth doing until it is settled.

  2. 2

    Register it

    The carrier paperwork every US business texting number needs. Weeks, not minutes, and largely outside your control once submitted, which is exactly why it should not be the thing you discover last. Unregistered traffic is filtered rather than refused, so it fails quietly.

  3. 3

    Know which rules bind you

    Federal rules are the floor and several states sit above them. If you serve more than one state, the strictest one is the one to build against, because a per-state send policy is a bug waiting to happen.

  4. 4

    Then automate, carefully

    Reminders and follow-up, with quiet hours and a frequency cap. Getting this wrong costs more than a complaint: a number people report is a number carriers stop trusting, and that is slow to undo.

What is not here

No case studies and no customer quotes, because we do not have real ones with permission yet and inventing them is not on the table. Nothing here is legal advice either: the compliance writing is what we had to learn to build the send path, which is a different thing from what your attorney will tell you about your own business. And none of it covers reading your reviews back from Google or syncing an outside calendar, because Frontiva does not do either yet and the integrations page says so.

Start free. Be live this week.

Built for dental, med spa, home services, and the businesses that live on the phone.