Skip to content
SAVE4545% off every plan.See the offer

Integrations & Setup GuidesCommunication Integrations

Communication Integrations

AutomateNexus CRM supports multiple communication channels beyond email, enabling you to reach contacts via SMS, voice calls, push notifications, and…

On this page· 38

Overview#

AutomateNexus CRM supports communication channels beyond email: SMS and voice through your own Twilio account, WhatsApp through Twilio, lifelike voices from ElevenLabs and transcription from Deepgram, and web push notifications for your team. Leads from your Facebook and Instagram ads, the events you send to Meta, and the social accounts the Social Scheduler posts to are set up too. Text, voice, WhatsApp and website chat conversations come together in one inbox. This guide covers the setup of each channel available under Administration → Integrations → Communications, and of the Facebook and Instagram connections.

Prerequisites#

Before setting up communication integrations, ensure you have:

  • An owner or admin role in your AutomateNexus CRM organization for the organization's connections (Voice & SMS, WhatsApp, Email and Push notifications): other members can see what is connected but not change it. Your own mailbox needs no special role.
  • A Twilio account (for SMS, voice and WhatsApp), with a payment method on it: SMS and voice usage incurs per-message and per-minute charges billed by Twilio.
  • For Facebook and Instagram, a Facebook Page you can advertise for, and access to your Meta Business settings and Events Manager.
  1. Log in to your AutomateNexus CRM dashboard.
  2. In the sidebar, under Administration, click Integrations.
  3. Choose Communications in the left menu of the Integrations page.

The Communications section is arranged under headings: Voice & SMS (Twilio, Calls, ElevenLabs, Deepgram), WhatsApp, Email (Resend and Sending accounts), Push notifications and Your mailbox (your own Gmail or Outlook; see Email Integration Setup). Most cards expand to show their fields, have an on/off switch, and show Connected once they are set up. Facebook and Instagram lead forms and the Meta Conversions API are under Automation in the same left menu (see Facebook, Instagram and Meta Ads below).

Twilio SMS and Voice#

About Twilio#

Twilio provides the programmable phone line behind AutomateNexus CRM's SMS, voice and WhatsApp features: text conversations and SMS campaigns, the in-app softphone and Power Dialer, and the AI phone receptionist. One card covers SMS and voice.

Step-by-Step Twilio Setup#

  1. Log in to your Twilio Console at console.twilio.com.
  2. On the dashboard, locate your Account SID and Auth Token. Copy both values.
  3. Navigate to Phone Numbers → Manage → Active Numbers to find your Twilio phone number. If you do not have one, you can buy one in Twilio or, later, inside AutomateNexus CRM.
  4. In AutomateNexus CRM, navigate to Administration → Integrations → Communications and expand the Twilio card.
  5. Enter the following fields:
    • Account SID: Your Twilio Account SID.
    • Auth Token: Your Twilio Auth Token.
    • Phone Number: Your Twilio phone number in international format, with the plus and the country code (e.g., +12125550123 or +61489089613). Calls from the softphone show this number to the people you call.
  6. Click Save, then turn the card's switch on.

Phone Numbers#

Numbers live under Inbox → Communication Hub → Phone numbers. Use Find Available Numbers to buy a number in the United States, Canada or the United Kingdom, or Check Twilio under Numbers on your Twilio account to connect one you already own. A number bought or connected there has its messaging and voice webhooks set for you, with a second address Twilio falls back to if the first does not answer. See AI Phone Receptionist.

Where Calls and Texts Go#

  • Texts to your number land in Inbox → Communication Hub as SMS conversations. The person does not have to be in the CRM first; a text is linked to their record when their number matches one.
  • Calls to your number are answered by the AI phone receptionist when it is switched on. When it is not (it is switched off, it is off for that number, or its monthly minutes are used up), a call goes to the receptionist's forwarding number if you chose one; otherwise it rings your team in the softphone, once Browser calling below is set up. With neither, the caller hears that nobody can take the call.

Setting Up Inbound SMS and Voice by Hand#

For a number you manage in the Twilio console rather than in the app, point Twilio at AutomateNexus CRM yourself. The addresses on the Twilio card are on your CRM's own domain (for example https://app.automatenexuscrm.com/functions/v1/ai-sms-handler, or your agency's domain when you sign in there).

  1. On the Twilio card, copy the Inbound SMS webhook.
  2. In the Twilio Console, open Phone Numbers → Manage → Active Numbers and click your number.
  3. Under Messaging, set A message comes in to Webhook with the copied URL and the HTTP method POST.
  4. Back on the Twilio card, copy the Inbound Voice webhook, and under Voice set A call comes in to Webhook with that URL and POST.
  5. Save in Twilio. Incoming texts now appear in the inbox, and incoming calls reach the receptionist or the softphone as described above.

If the number belongs to a Messaging Service in Twilio, the service's own Integration setting decides where texts go, whatever the number says: in the Messaging Service, set Incoming Messages to Defer to sender's webhook, or paste the Inbound SMS webhook there. A number you pointed at the CRM before keeps working with the addresses it was given.

Browser Calling#

The in-app softphone and Power Dialer need a Twilio API key (separate from your Auth Token) and a TwiML Application. The Browser calling part of the Twilio card shows Not set up until these are saved:

  1. In the Twilio Console, go to Account → API keys & tokens and create a Standard API key. Paste its SID and secret into API Key SID and API Key Secret.
  2. Copy the TwiML App Voice URL from the card. In the Twilio Console, go to Voice → TwiML → TwiML Apps, create an app, and set its Voice URL to that address (HTTP POST).
  3. Paste the app's SID into TwiML App SID and click Save. The card then shows Configured.

Receiving Calls in the Browser#

  • Open the phone panel with the phone icon on the right-hand edge of the CRM. It says Ready when it can take calls. There is no separate online switch: it stays connected while you move around the CRM and switch between the panel's tabs, and closing the panel disconnects it.
  • Keep the CRM open in a browser tab and allow the microphone when your browser asks.
  • A call rings the softphone of everyone in your organization who has it open, all at once. The first to click Accept takes the call.
  • When nobody answers, the cell phones of the people who forward their calls ring, then the caller can leave a voicemail. See Communication Hub for how long the app rings, forwarding to a cell phone, voicemail, transfer and hold.

Calls You Place#

Calls from the softphone and the Power Dialer show the number in the Twilio card's Phone Number field as the caller ID, or, with none there, one of the organization's numbers under Phone numbers. Dial a number with its country code, or the way it is written locally: a local number is read in your workspace's country, which comes from your own phone number unless you choose another under Settings → Organization → Phone numbers.

Voice Settings#

Settings for the calls your team takes and places in the softphone (recording, transcripts and summaries, how long the app rings and voicemail) are on the Calls card, next to the Twilio card under Voice & SMS. Each person chooses under Settings → Voice & calls → Calls I miss whether the calls they miss ring their cell phone too. The AI phone receptionist has its own settings under AI → AI Team → Receptionist → Settings. See Communication Hub and AI Phone Receptionist.

ElevenLabs and Deepgram#

  • ElevenLabs — The voice your phone receptionist speaks in. Expand the card, paste an API Key from elevenlabs.io → Settings → API Keys, click Save and turn the card on. The voice itself is chosen in the receptionist's settings under AI → AI Team → Receptionist → Settings, in Language and voice.
  • Deepgram — Transcription that labels who said what. Expand the card, paste an API Key from console.deepgram.com → API Keys (new accounts come with free credit), click Save and turn the card on. It is used when a meeting is recorded with In the cloud → Deepgram Nova-3, and recorded phone calls are transcribed with your key too, instead of on your AI credits. Deepgram bills your account. See AI Meeting Notes.

WhatsApp#

WhatsApp connects one of two ways, and messages land in the inbox next to SMS and email either way:

  • Straight through Meta: your own Meta app and WhatsApp Business number, with no Twilio in between. Meta bills you directly, and replies within 24 hours of a customer's message are free.
  • Twilio: through your own Twilio account, like SMS.

Every WhatsApp feature works the same either way: the inbox, automatic replies and buttons, templates, campaigns, workflows, follow-ups, review requests and the AI assistant. Only an owner or admin can change it.

Straight Through Meta#

You need a Meta app with WhatsApp added and your WhatsApp Business number on it (developers.facebook.com → your app → WhatsApp → API Setup).

  1. Expand the WhatsApp card under the WhatsApp heading and choose Straight through Meta under Connect through.
  2. From WhatsApp → API Setup in your Meta app, copy the Phone number ID and the WhatsApp Business account ID into the card.
  3. Make a permanent Access token: in Meta Business settings → System users, add a system user, give it your app and your WhatsApp account, and generate a token with whatsapp_business_messaging and whatsapp_business_management. Paste it in.
  4. Copy the App secret from your app's App settings → Basic.
  5. Click Check and turn on. The CRM checks everything with Meta, connects your WhatsApp account to your app and points the app's webhook at the address on the card. When all is well, WhatsApp switches on and the card shows your number and its name. Anything Meta turns down is listed on the card in plain words.

If the card asks for a Two-step PIN, your number is not registered for sending yet: enter the 6-digit PIN set for it in WhatsApp Manager (or choose one), and click Register number.

If your app's webhook already points somewhere else, the card says so and leaves it alone. To move it here, open WhatsApp → Configuration in your Meta app, paste the card's Webhook address and Verify token, and subscribe to messages.

Moving from Twilio? WhatsApp keeps going through Twilio until the check passes; the button then reads Check and switch to Meta. Templates stay where they were made, so make yours again on the Templates tab and choose the new ones in campaigns, workflow steps and review requests. Templates you made in WhatsApp Manager show on the Templates tab too.

Through Twilio#

Connect Twilio under Voice & SMS first; through Twilio, the WhatsApp card cannot be turned on until Twilio is connected and switched on.

  1. Expand the WhatsApp card under the WhatsApp heading and choose Twilio under Connect through.
  2. Under Sending from, choose:
    • Twilio Sandbox — For trying it today, with no approval needed. Each person first sends your Sandbox join code to the sandbox number shown on the card.
    • Your WhatsApp Business number — A WhatsApp sender registered in your Twilio console (Messaging → Senders → WhatsApp senders). Enter it in WhatsApp sender number, exactly as registered in Twilio, in full international format (for example +15551234567).
  3. Copy the Incoming message webhook. It is on your CRM's own domain (for example https://app.automatenexuscrm.com/functions/v1/whatsapp-webhook?org=…, or your agency's domain when you sign in there). In Twilio, paste it, with HTTP POST, into When a message comes in under Messaging → Try it out → Send a WhatsApp message → Sandbox settings for the Sandbox, or into Webhook URL for incoming messages on your WhatsApp sender.
  4. Click Save and turn on (Save and switch to Twilio when WhatsApp goes through Meta now). The card shows Connected, or Sandbox while you use the Sandbox.

WhatsApp's Rules#

  • Replies to someone who wrote in the last 24 hours can be free text.
  • After that, WhatsApp only delivers a template it has approved, and only to people whose WhatsApp opt-in is recorded on their contact or customer record. Templates are made on the Templates tab of Marketing → WhatsApp and sent to WhatsApp for approval from there, or made in WhatsApp Manager (straight through Meta) or Twilio's Content Template Builder (through Twilio). The card counts the approved templates on your account.

To test, send a WhatsApp message to your sender from your phone. It appears in the inbox under Inbox → Communication Hub, where you can reply.

Push Notifications#

About Push Notifications#

AutomateNexus CRM sends web push notifications to team members' browsers and computers for the events they have turned on, such as messages taken by the phone receptionist. Push works through the web app once each person has enabled it. It is sent with the platform's own keys unless your organization adds its own.

Using Your Own Push Keys#

This is optional.

  1. Navigate to Administration → Integrations → Communications → Push notifications.
  2. Generate a VAPID key pair with npx web-push generate-vapid-keys, or at vapidkeys.com.
  3. Expand the card, paste the VAPID Public Key and VAPID Private Key of the same pair, click Save, and turn on the switch (Use your own push keys). New devices then subscribe with your keys.

Switched off, new devices subscribe with the platform's keys, and devices that subscribed with yours are still reached. Replace both keys together: a public key only works with the private key it was made with.

Per-User Notification Settings#

Each team member controls their own notifications:

  1. Open Settings → Notifications.
  2. On the Preferences tab, toggle in-app notification types on or off.
  3. On the Push tab, allow the Browser Permission when asked and switch on Enable Push Notifications. Push notifications need a modern browser such as Chrome, Firefox or Safari.

Facebook, Instagram and Meta Ads#

Social Accounts for the Social Scheduler#

The accounts you post from are connected in the Social Scheduler itself, with a sign-in on each network; there are no app credentials to paste.

  1. Navigate to Marketing → Social Scheduler.
  2. On the Compose tab, click Connect a channel (or Manage beside your channels) to open Channels, then click Connect Account.
  3. Choose the network: Facebook Pages, Instagram (business or creator accounts linked to a Facebook Page), LinkedIn, X (Twitter), TikTok, YouTube or Google Business Profile. A network that is not available yet says so.
  4. Sign in on the network, then choose what to connect to this workspace. The account appears under Connected Accounts.

Once connected, you compose and schedule posts from the Social Scheduler, and its Inbox tab collects comments and mentions from your connected accounts for you to reply to, with AI suggest to draft a reply.

Lead Forms from Facebook and Instagram Ads#

Every lead from your Facebook and Instagram instant forms can arrive in the CRM at once: a contact with every answer, the form and the ad it came from, and the consent it gave. Owners and admins connect lead forms.

  1. Navigate to Administration → Integrations → Automation and find Facebook and Instagram lead forms under Lead forms.
  2. Click Connect with Facebook and sign in as someone who can advertise for the Page. Instagram lead forms run on its Facebook Page.
  3. Choose the Page whose lead forms send their leads here.
  4. Choose where its leads go under Leads go to (the main workspace, or another), and who New leads are owned by.
  5. Under each form, match its consent checkboxes to what they mean (for example Agrees to WhatsApp messages): WhatsApp delivers a first message to a lead only when its WhatsApp opt-in is recorded.
  6. Click Send a test lead on a form. It arrives in People in a few seconds, with its answers.

Pause keeps new leads in Facebook until you click Resume, and Check connection asks Facebook whether this Page's leads are being sent. Speed to lead, one of the workflow templates, answers each new lead in seconds. If the card says Facebook lead forms are not switched on yet, Zapier or Make can send your Facebook leads in instead; see Automation Platform Connections.

Ad Conversions: the Meta Conversions API#

The Meta Conversions API sends your leads, bookings and purchases to Meta from the server, alongside your pixel, so your ads keep measuring results when a browser blocks tracking.

  1. Navigate to Administration → Integrations → Automation and find the Meta Conversions API card under Ad conversions.
  2. Click Set up (owners and admins).
  3. In Meta Events Manager, open your dataset's Settings and copy its Dataset ID (a dataset is what Meta now calls your pixel). Paste it in.
  4. Still in Settings, under Conversions API, use Set up direct integration → Generate access token, and paste the token (it starts with EAA). If Meta says an email is missing, add yours in Business settings under Business info first.
  5. Click Check with Meta, choose what to send (Leads, Bookings, Purchases and Lead-ad quality) and whether to Put your pixel on your CRM pages (checkouts, booking pages, forms and your website; it waits for the cookie banner where you have one), then click Start sending.

The card then shows what Meta received in the last 7 days, Meta's match quality, how many events were paired with your pixel, and anything that needs a look. Its switch pauses sending; events that waited go when you switch it back on. Open takes you to the Conversions tab of Marketing → Meta Ads, with its Overview, Events, Test events and Settings.

Meta Ads in the CRM#

Marketing → Meta Ads shows your Facebook and Instagram ads without opening Ads Manager: spend, results and what each ad brought into the CRM, with alerts when an ad is rejected, a payment fails or a budget runs low, and a summary every Monday. It has Results, Conversions and Settings tabs.

  1. Click Connect your ad account (owners and admins).
  2. Make a token in Meta's Business settings → Users → System users: add a system user, use Assign assets to give it Full control of your app and Manage campaigns on your ad account, then Generate token for that same app, set to Never expire, with ads_read and ads_management ticked. The dialog lists each step.
  3. Paste the token, choose the ad account, and let Meta check it. The first read takes up to a minute.

With ads_management on the token, you can pause and resume ads and change budgets from the CRM; each change asks you to confirm first and is logged. A token with ads_read only reads results.

Unified Inbox#

Text, voice, WhatsApp and website chat conversations converge in the Communication Hub:

  1. Navigate to Inbox → Communication Hub and open Inbox.
  2. The inbox lists conversations across SMS, Email, Call, WhatsApp and Website chat, with a channel filter (All channels by default).
  3. Reply in the thread, and AutomateNexus CRM sends the response through the conversation's channel; a WhatsApp reply can carry an attachment.
  4. Start a new SMS, WhatsApp or email conversation with a contact from the same inbox.

Support conversations, including website chat, also appear under Inbox → Support Hub → Inbox.

Testing Communication Integrations#

  1. Test SMS: start a new SMS conversation to your own mobile from Inbox → Communication Hub → Inbox. Verify delivery, then text your Twilio number back from the mobile and check that your text appears in the same thread.
  2. Test a call you place: with Browser calling configured, place a call to your own phone from Inbox → Communication Hub → Dialer. Verify audio quality and that the call appears under Calls.
  3. Test a call that comes in: open the phone panel (the phone icon on the right-hand edge of the CRM) and wait for Ready, then call your Twilio number from your mobile. With the AI phone receptionist off, the panel shows Incoming call with Accept and Reject; with it on, the receptionist answers.
  4. Test Push Notifications: enable push on Settings → Notifications → Push, then trigger an event that notifies you, such as a message taken by the phone receptionist.
  5. Test Social Media: schedule a post from the Social Scheduler and check that it publishes to the connected account.

Troubleshooting#

SMS Not Sending#

  • Verify your Twilio Account SID and Auth Token are correct and the Twilio card is switched on.
  • Check that your Twilio account has sufficient balance for SMS charges.
  • Check the recipient's number: one saved with its country code is always sent as written; one saved without is read in your workspace's default country, under Settings → Organization → Phone numbers.
  • For US/Canada numbers, verify you have completed A2P 10DLC registration in Twilio (required for business SMS).
  • Check Twilio error logs at Monitor → Logs → Errors in the Twilio Console.

Incoming Texts Not Appearing#

  • Look in Inbox → Communication Hub → Inbox: every text that reaches the CRM is filed there as an SMS conversation.
  • In the Twilio Console, check that the number's A message comes in is the Inbound SMS webhook from the Twilio card, with POST.
  • If the number belongs to a Messaging Service, set the service's Incoming Messages to Defer to sender's webhook (or paste the webhook there): otherwise the service sends texts somewhere else.
  • Check the Phone Number on the Twilio card is the number being texted, or that the number is listed under Inbox → Communication Hub → Phone numbers.
  • In the Twilio Console, Monitor → Logs → Messaging shows each incoming text; a webhook error on it (11200) means the CRM was reached and refused it.

Incoming Calls Not Ringing the Softphone#

  • Check that the AI phone receptionist is off for the number, and that it has no forwarding number: while it is on, it answers instead, and with a forwarding number, the call goes there.
  • Make sure Browser calling shows Configured on the Twilio card and the card is switched on.
  • Open the phone panel and wait for Ready, in a browser tab with the CRM. Closing the panel disconnects it.
  • In the Twilio Console, check that the number's A call comes in is the Inbound Voice webhook from the Twilio card, with POST, or connect the number from Inbox → Communication Hub → Phone numbers, which sets it for you.

Calls You Place Failing Straight Away#

  • Check that the Twilio card's Phone Number is one of your Twilio numbers, written with the plus and the country code: calls show it as the caller ID.
  • In the Twilio Console, open Voice → Settings → Geo permissions and make sure the country you are calling is allowed, mobile numbers included.
  • Open the failed call in Monitor → Logs → Calls: its error code says why Twilio stopped it (13214 is the caller ID, 13227 a Geo permission).

Voice Calls Dropping or Poor Quality#

  • Make sure Browser calling shows Configured on the Twilio card: the API Key SID, API Key Secret and TwiML App SID are all needed.
  • Ensure you have a stable internet connection with sufficient bandwidth.
  • Allow microphone access in your browser when prompted.
  • Check that your browser supports WebRTC (Chrome, Firefox, Edge are recommended).
  • Disable VPN connections that may introduce latency.

Social Media Posts Not Publishing#

  • Verify the account still appears under Connected Accounts in the Social Scheduler; disconnect and reconnect it if its authorization has lapsed.
  • For Facebook and Instagram, ensure the connected account still has admin access to the Page and the Page is published.

Push Notifications Not Appearing#

  • Ensure browser notifications are allowed for the AutomateNexus CRM domain and Enable Push Notifications is on under Settings → Notifications → Push.
  • Check that the VAPID keys are saved and the Push notifications card is switched on under Administration → Integrations → Communications.
  • Check that the notification type is turned on in your Preferences.

Was this page helpful?

Last updated