Connect the channels your customers already use.
We label every integration by what it actually does today - Live, Partially live, or Coming soon - never as available before it is.
SMS (Telnyx or Twilio)
LiveFully wired end to end on either carrier: inbound texts, AI or human replies, outbound sends, STOP/START handling.
DetailsWebsite Chat
LiveOne script tag on your own site. Visitors are answered from your approved knowledge and every chat lands in the shared inbox as a contact and a lead.
DetailsConnect the mailbox you already have over IMAP and SMTP. New mail becomes a conversation; replies go back out from the same address.
DetailsSend and receive both work today; a self-serve connect flow is still shipping.
DetailsFacebook Messenger
Partially liveSend and receive both work today; a self-serve connect flow is still shipping.
DetailsSend and receive both work today; a connect flow and 24-hour-window template sends are still shipping.
DetailsGoogle Calendar
Coming soonTwo-way sync for staff calendars, part of Bookings.
DetailsMicrosoft 365
Coming soonCalendar sync for teams on Outlook/Microsoft 365, part of Bookings.
DetailsStripe
Partially liveHow we bill you is built: hosted checkout, invoices and receipts, no card details reaching us. Taking deposits from your own customers is still coming.
DetailsGoogle Business Profile
Coming soonReview monitoring and AI-suggested responses, part of Reviews.
DetailsAPI and webhooks
LiveConnect your own software: scoped API keys, and signed webhooks that tell it when something happens here.
DetailsWhat each one needs from you, and what it still cannot do
Both columns are the things you would otherwise find out after signing up. Setting a channel up is somebody's afternoon, and it is worth knowing whose afternoon and which console before you start, so the second column names what is missing instead of leaving a label to imply it.
| Connection | What you provide | What it cannot do yet |
|---|---|---|
| SMS (Telnyx or Twilio) | An account with one of the two carriers, and the choice is yours because which one registers your business depends on where it is incorporated. Telnyx: a number in E.164 form and one API key. Twilio: the number, the Account SID, the auth token, and two webhook URLs Frontiva prints for you to paste into their console. Either way the account is yours, so carrier charges reach you at carrier rates rather than marked up through ours. | We cannot provision a number for you, and we cannot file your A2P 10DLC registration on either carrier. Frontiva tracks that registration and records the carriers' answer against it, so you find out a number would be filtered before you find out by being filtered. Connecting both carriers at once is refused rather than used as a fallback, and the page says why. |
| Website Chat | A widget key you generate on the Integrations screen, and one script tag before the closing body tag of your pages. No DNS record, no mailbox, no plugin. | No attachments in either direction, no typing indicator for the visitor, and the bubble cannot yet be called anything but Chat with us. Emailing a transcript to the visitor is deliberately not planned until it can be tied to consent the visitor gave. |
| The mailbox address and an app password, plus the IMAP and SMTP hostnames, which fill themselves in for Hostinger, Google Workspace and Microsoft 365. One folder to watch, INBOX unless you name another, and optionally a different reply address and sender name. | There is no Google or Microsoft OAuth button yet, so an app password is needed. Attachments stay in the mailbox and arrive here as a name, a type and a size. Nothing imports your existing mail, and the agent does not reply on this channel at all. | |
| The Page ID and a page access token. In practice that means we connect it with you rather than you doing it alone, which is the honest reading of the Partially live label on its card above. | The self-serve connect flow, because that needs Meta's app review. Sends outside Meta's messaging window need message tags that are not modelled yet. | |
| Facebook Messenger | The Page ID and a page access token, the same pair as Instagram and with the same caveat: today we do it with you. | The self-serve connect flow, because that needs Meta's app review. Sends outside Meta's messaging window need message tags that are not modelled yet. |
| The phone number ID from your WhatsApp Business account, and a token. | The self-serve connect flow, and approved template sends, which is what a reply outside WhatsApp's 24 hour customer service window needs. Until those exist, a conversation that has gone quiet for a day cannot be reopened from here. | |
| Google Calendar | Nothing, because there is nothing to connect. Bookings runs on the rotas, buffers and time off you set here in the meantime, and the database refuses a double booking rather than apologising for one. | All of it: importing busy time so an outside commitment blocks a slot, and pushing an appointment back the other way. It ships with Bookings. |
| Microsoft 365 | Nothing for calendar. One thing worth knowing: a Microsoft 365 mailbox connects today as email, because the mail presets already carry outlook.office365.com and smtp.office365.com, so a team on Outlook is not waiting on this row to use the shared inbox. | Calendar sync, alongside Google Calendar and for the same reason. |
| Stripe | Nothing from you. This is the connection Frontiva uses to bill you, on Stripe's own hosted checkout, which is why no card number ever reaches us. | It is idle rather than merely incomplete: until Frontiva connects its own Stripe account and the plans carry published prices, there is nothing on your Billing screen. Taking deposits from your customers is a different Stripe product again, so a booking deposit policy is shown to your customer and never charged, and the booking page says so. |
| Google Business Profile | Nothing, because there is nothing to connect. | All of it, and this is the gap worth stating plainly rather than softening: Frontiva cannot read your reviews back, so there is no monitoring, no suggested reply and no rating trend anywhere in the product. Asking a customer for a review works today, on its own separate opt-in, and is a different thing. |
| API and webhooks | An API key you create and scope yourself, and your own HTTPS address if you want webhooks. The key is shown once and kept only as a fingerprint, so nobody here can read it back to you or to anyone claiming to be you. | Incoming webhooks, so another system can push events to us the way we push them to you. Everything today goes one way out. |
Three of these carry a cost that is not ours to charge, and they are worth planning for: a Telnyx or Twilio number and its per-message carrier fees, a 10DLC brand and campaign registration with its own one-off and monthly carrier charges, and a WhatsApp Business account. Website chat, email and the API cost nothing beyond what you already pay for your site and your mailbox, which is why those three are the ones you can have working this afternoon.
What those three labels mean
Every integrations page on every website says "coming soon" about something. These are the definitions we hold ourselves to, so the labels above are checkable rather than decorative.
- Live
- You can connect it yourself today, and messages move in both directions without us touching anything. SMS, website chat, email and the API are here.
- Partially live
- The hard half works and one named piece does not. The three Meta channels send and receive against a real app; what is missing is the self-serve connect flow, because that needs Meta's app review. Stripe bills you through hosted checkout; taking deposits from your customers is the part still coming.
- Coming soon
- Not built. There is an adapter and a mock behind it and no provider on the other end, so nothing works and the page says so. Calendar sync and reading reviews back are both here, and both are honestly the biggest gaps in the product.
The accounts stay yours
This is the part worth understanding before you sign up, because it decides what you have to do and what it costs.
Texting runs on your own carrier account, Telnyx or Twilio. You enter the number and the credentials that carrier issued you on the Integrations screen, and the carrier charges land on your own bill rather than being marked up through ours. The number stays yours, which also means you keep it if you leave. The consequence is honest and cuts the other way too: we cannot provision a number for you, and we cannot submit your A2P 10DLC registration, which is the carrier paperwork every US business texting number needs. The product tracks that registration and records the carriers' answer against it, so it can tell you a number would be filtered before you find out by being filtered.
Email runs on the mailbox you already have. An address, a password and two hostnames over IMAP and SMTP, one watched folder, and new mail becomes an ordinary conversation in the shared inbox. Replies go out from that same mailbox with a Reply-To pointing back at it, so a customer's thread stays in one place. Three limits, stated rather than discovered: there is no Google or Microsoft OAuth button yet, so you need an app password; attachments stay in the mailbox and arrive here as a name, type and size; and nothing imports your existing mail, so a connected mailbox starts from now.
Website chat needs nothing but a script tag. One line on your own site, and a visitor is answered from your approved knowledge while the conversation lands in the inbox as a contact and a lead.
What the AI will and will not do per channel
The channel decides the behaviour, deliberately, and it is not a setting we hide.
- Text and website chat: the agent answers, from approved facts only, with the source shown beside the reply and approval mode on until you decide otherwise.
- Email: it arrives, it is threaded, a person replies. There is no AI reply on email, which is a choice rather than an omission: an email is where somebody writes the long complicated thing, and that is the worst possible place to guess.
- Instagram, Messenger and WhatsApp: messages arrive and can be answered. For a business with patients the rule is stricter and enforced in code, not in a policy document: no AI-composed reply goes out on a Meta channel for a healthcare tenant, because Meta signs no BAA.
- Marketing: email campaigns are allowed and text campaigns are refused outright, because a marketing text needs express written consent this product does not capture. A review request is the one exception and it has its own separate opt-in.
If what you use is not listed
Scoped API keys and signed webhooks are the answer, and they are live. Your software asks Frontiva for contacts, leads and appointments, and Frontiva tells your software when something happens here, signed so it can verify the message came from us. That is the route for the practice management system or the field service tool that will never be on a list like this one.
Start free. Be live this week.
Built for dental, med spa, home services, and the businesses that live on the phone.