Skip to content

Integrations · Messaging

Text messages from your own number, through Twilio

Staff text someone from their record or the shared inbox, replies come back into the same conversation, and every text is kept on the person’s record. The number and the account stay in your organisation’s name.

What it does in Affinux

  • Sending

    • Text a person from their record, from the shared inbox, or as a step in an automation.
    • More than one number, each marked for replies, for campaigns, or both.
    • Checks before sending: a number that is a landline, and a message long enough to go as several texts.
    • Text campaigns to people who agreed to hear by text, with the opt-out wording added.
  • Receiving

    • Replies arrive in the shared inbox, in the same conversation as the text they answer.
    • A text is linked to the person who holds that number, and a number nobody holds can create a new person where the inbox is set to.
  • Keeping track

    • Each text’s delivery shown on it, and a failure explained in plain words, such as “Not a mobile number” or “They replied STOP to the sending number”.
    • STOP and START handled by themselves; anyone who replied STOP is not texted from that number again.
    • How much is left on the Twilio account, on the organisation’s channel settings, shown in amber when it runs low.

Set it up in three steps

  1. Connect your Twilio account

    Add your organisation’s own Twilio account in Affinux. The number and the account stay in your name.

  2. Say what each number is for

    Mark each number for replies, for campaigns, or both.

  3. Text someone from their record

    Replies arrive in the shared inbox, in the same conversation as the text they answer.

Where a text goes

Nothing lives on one person’s phone.

  1. Someone texts your numberor replies to a text you sent
  2. Twilio receives iton your organisation’s own account
  3. It arrives in the shared inboxin the same conversation, for the team to assign and answer
  4. Affinux files iton the record of the person who holds that number

Phone calls in the browser

Phone calls answered and made in the browser, with no desk phone. Calls to the organisation’s number wait in a call queue until someone available picks up, missed calls and voicemails become calls to return, and every call is on the call log and the caller’s record.

We set this up with you. Talk to us

  • Lines and call queues

    • One or more phone numbers, each with its greeting, hold music and opening hours, with more than one opening a day.
    • Call queues that choose who answers: ring everyone, whoever has waited longest, in turn, or whoever has taken fewest calls today.
    • A target time to answer, and a longest wait, after which the caller can leave a voicemail or be put through to another number.
    • Greetings, hold music, voicemail and closed messages as typed words or a recording, and “Hear it as a caller” to ring a mobile and listen.
    • Outside opening hours, a closed message that can say when the line opens next.
  • Answering

    • A phone in the browser that rings on any page, showing who is calling where the number is known.
    • Staff choose Available or Away; someone who closed the browser while Available comes back as Away.
    • Pass a call to a colleague or another call queue, with a note for whoever takes it.
    • A short time after each call to write it up before the next one rings.
  • Calling out

    • Call a person from their record, with the call logged against them.
    • Premium numbers and emergency numbers are refused, and calls abroad only go to countries allowed on the line.
    • A monthly limit for each line, and a person’s wish not to be phoned is respected.
  • After the call

    • Missed calls, callers who hung up waiting and voicemails go on a list to call back, and whoever rings back first is shown to colleagues.
    • A live board of who is available, ringing, on a call or writing up, and of callers waiting.
    • Reports for each call queue: calls in, answered, hung up waiting, answered within target, and average wait and talk time.
  • Recording

    • Call recording, off unless switched on, for all calls, calls in or calls out, with an optional notice to callers.
    • Recordings kept for 30, 90, 180 or 365 days; voicemails for 90.

Control and safety

  • Sending texts needs its own permission; staff can be allowed to send without changing campaigns or settings.
  • Marketing texts check consent by purpose before they go.
  • Every text, in or out, is on the person’s timeline for staff allowed to see it.
  • Answering, calling out, watching the live board, listening to voicemails and playing recordings are separate permissions.
  • A recording plays only for staff allowed to, and by default only for the person who took the call; each play is logged.

Good to know

  • Callers cannot yet press a key to choose an option.
  • Twilio charges your organisation for texts and calls, on your own Twilio account.
  • We switch calling on for each organisation. Tell us if you want it.

Questions about Twilio and Affinux

Do we need our own Twilio account?

Yes. Texts go through your organisation’s own Twilio account, so the number and the account stay in your name.

What happens when someone replies STOP?

STOP and START are handled by themselves. Anyone who replied STOP is not texted from that number again.

Can we take phone calls through Twilio too?

Yes. Calls are answered and made in the browser, with call queues, voicemail and calls to return. Tell us you want calling, and we switch it on for your organisation.

See how Affinux would work for your team

A 30-minute demo, shown with your type of organisation. Or start a free trial and explore with sample data.