Integrations: how SIAS gets your calls into your CRM, your website and your calendar

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.

Standard delivery, included in every plan

ChannelWhat you getTypical use
Text message (SMS)The message, as filed by the operator, to one or more phonesOn-call techs, agents, managers
EmailThe message, with the caller's name, number and the details your script asks forOffice inbox, shared mailboxes, ticketing systems that accept email
FaxThe message as a fax pageMedical and legal offices that still route by fax
Online portalEvery message on your account, viewable any timeOwners and office managers checking the day's calls
Secure Delivery appMessages behind a login, for browser, Android and iPhoneProtected health information, confidential legal matters
Paging and calloutsThe operator pages or calls your on-call list in order until someone answersAfter-hours emergencies
Live transfer (patch)The caller is connected to you; operator time stops when the connection is madeSales 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.

CRM write-back: the message becomes a contact and a note

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:

  1. The operator takes the call on the account's script and files the message in our switch, exactly as for any other account.
  2. The workflow receives the message and searches the CRM by the caller's phone number. One clear match: that contact is used. No match: it checks a lookup list we maintain for the account, which is updated every time a contact is found or created.
  3. If neither finds the caller, a new contact is created with the name, number and address the operator captured.
  4. The message is written to the contact as an activity note, so the salesperson sees the call history on the record, not in a separate inbox.
  5. The workflow stops for manual review only when the same phone number is attached to more than one contact and it cannot safely pick one. A different spelling of the name or a new email address is not a reason to create a duplicate.

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.

Website lead delivery: the message goes through your own lead form

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 and estimate scheduling

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.

How a custom integration is built

  • Discovery. We look at how your team works today (which system, which fields, who needs to see what) and at the API or form on your side. If something cannot be done reliably, we say so before we start rather than build a workaround that breaks later.
  • Build and test. The workflow runs on our automation platform, which reads the operator's filed message and talks to your system. We test with real messages before the operators are told anything changes.
  • Operator instructions. Operators keep filing messages the way they always have; the integration takes over after that. For the roofing client the only change on the floor was a reminder to capture the address on every call.
  • Monitoring. Failed submissions and ambiguous matches are flagged for a person to handle, and we review the first weeks of output with you.

What integrations cost

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.

To talk through an integration, call (815) 741-2007 or email [email protected]. Plans and standard delivery are on the plans page; prices and billing rules are in Pricing and Plans Explained. Special Interest Answering Service is family-owned, based in Joliet, Illinois, founded in 1980, and not affiliated with Specialty Answering Service (SAS).

Integration questions

Does SIAS integrate with my CRM?

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.

Can messages go straight into my website's lead form?

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.

Do the operators have to do anything different?

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.

Is the integration included in the plan price?

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.

What happens if the integration fails on a call?

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.

Can I get my call data?

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).

Contact Us

Call: 815.741.2007 or 815.846.3320

Fax: 630-570-7606