Every Special Interest Answering Service (SIAS) account gets its messages by text, email, fax or our online portal, with a Secure Delivery app for anything that should not travel in plain text. For businesses that run on a CRM, we go one step further: the operator files the message and it lands in your system as a contact and a note, or in your website's lead form, within seconds, with no retyping. This page explains what is standard, what we have built for clients, and how a custom integration is set up and priced.
| Channel | What you get | Typical use |
|---|---|---|
| Text message (SMS) | The message, as filed by the operator, to one or more phones | On-call techs, agents, managers |
| The message, with the caller's name, number and the details your script asks for | Office inbox, shared mailboxes, ticketing systems that accept email | |
| Fax | The message as a fax page | Medical and legal offices that still route by fax |
| Online portal | Every message on your account, viewable any time | Owners and office managers checking the day's calls |
| Secure Delivery app | Messages behind a login, for browser, Android and iPhone | Protected health information, confidential legal matters |
| Paging and callouts | The operator pages or calls your on-call list in order until someone answers | After-hours emergencies |
| Live transfer (patch) | The caller is connected to you; operator time stops when the connection is made | Sales calls, urgent clients |
Any of these can be combined per message type. A common setup is a text to the on-call tech plus an email to the office for every emergency, and email only for routine messages. You change it by calling or writing in, and the change takes effect once we update your account.
For a roofing contractor that runs its sales and service work in JobNimbus, we built a workflow that takes each message the operator files and puts it where their team already works. It has run since April 2026 and was tightened in July 2026 to cut duplicate contacts. The steps:
JobNimbus is the CRM we have built this for. The same pattern applies to any CRM whose API can search contacts and add a note or activity; what your system's API allows decides what is possible, so we confirm that before quoting.
For a home builder that routes every sales inquiry through a form on its website, we built a workflow that watches for sales-lead messages from the operators, parses them, and submits them to the builder's website form as if the caller had filled it in. From there the builder's own notifications, CRM sync and sales follow-up run exactly as they do for a web lead. It went live in October 2026. If a submission fails, the workflow emails the owner of SIAS so the lead is handled by hand the same day; nothing is silently dropped.
This is the right pattern when a client already has a lead form wired to the tools they use (Gravity Forms, HubSpot forms, Typeform, a custom form). We post to the form; the client changes nothing on their side.
Appointment scheduling is available case by case, depending on how complex the booking is, and when we take it on it is billed as ordinary operator minutes, not as a per-booking fee. You tell us the slots you offer and what the caller needs to provide, and the operator books it on the call. The booking reaches you the same way as any message.
Scheduling directly inside a CRM's own calendar or task system (for example JobNimbus tasks) is a custom build. Our approach is to build and test it with the client at no charge first, and only then agree a per-verified-appointment price, so that we charge for a process that is proven to work for both sides.
Custom integrations are quoted per account: a one-time setup fee that covers the build and testing, plus a monthly maintenance fee, because the API on your side and the tools on ours change over time. Standard delivery (text, email, fax, portal, Secure Delivery app, paging, patch) is included in every plan. Our service stays contract-free; the setup fee is what covers the development time. Ask for a quote with your CRM's name and we will tell you whether we have built for it before.
If your CRM has an API that can search contacts and add a note or activity, it can be done. JobNimbus is the system we have a working build for. Tell us which CRM you use and we will confirm what its API allows before quoting.
Yes. We parse the operator's message and submit it to your form, so your existing notifications and CRM sync run as they do for any web lead. Failed submissions alert us by email the same day.
No. They take the call on your script and file the message as usual; the integration starts after that. The only change we have needed so far is reminding operators to capture a field your system requires, such as the property address.
No. Standard delivery is included. A custom integration has a one-time setup fee for the build and testing and a monthly maintenance fee. Scheduling inside a CRM calendar is tested at no charge first and then priced per verified appointment.
The message still exists in our system and reaches you by your normal delivery channels. A failed submission is flagged to us, and the message is handled by hand that day.
Yes. Every message is in your online portal, and we can export your message history as a spreadsheet on request.
Client examples on this page describe real SIAS builds (April and October 2026) without naming the clients. Delivery channels and scheduling terms as of October 27, 2026. Special Interest Answering Service is not affiliated with Specialty Answering Service (SAS).
Call: 815.741.2007 or 815.846.3320
Fax: 630-570-7606