Quo is the business phone system your team calls and texts from. Connect it once, and matching conversations show up on contact and deal records in Ariyel—next to email, meetings, notes, and tasks. Your team keeps using the Quo app; Ariyel holds the history on the record.
Once Quo is connected, Workflows can also send texts and react to Quo events (text received, call completed, call summary ready, contact opted out).
Quo triggers only fire for what What to bring in syncs: text received needs Texts; call completed and call summary ready need Calls, and call summary ready also needs AI call summaries.
Connect Quo#
Before you start: connecting needs an Ariyel workspace owner or admin, and generating the API key needs a Quo owner or admin.
- Open Settings → Apps, then open Quo (or choose Connect on the Apps list). Only owners and admins see Connect; other members see “Ask an owner or admin to connect Quo.” While Dialpad is connected, Connect is unavailable and reads Disconnect Dialpad first: a workspace connects one phone app at a time. If Apps can’t read the Quo connection, it says Could not load Quo’s connection. Please try again. with Retry, and Connect stays unavailable until it loads.
- In Quo, open Settings → API, generate a key (name it Ariyel so you can find it later), and paste it into the connect dialog.
- Choose how much history to import: Last 90 days (recommended), Last 60 days, or Last 30 days, then Connect.
Ariyel checks the key with Quo, loads your lines, and starts importing history. Quo then shows Connected on the Apps list; choose Manage to return to it. If Quo rejects the key, the dialog says Invalid Quo API key. Check the key in Quo and try again. Other connect, refresh, retry-import, and disconnect refusals also show as plain sentences, never as a raw code.
The integration syncs all lines in the connected Quo workspace; add or remove lines in Quo.
Any paid Quo plan works for calls and texts. AI call summaries need Quo’s Business plan or higher.
For help with the Quo integration, use Contact Educo on the Quo page in Settings → Apps, or Contact support on its About tab once connected. Both email hello@ariyel.io.
Connection health and history import#
The Connections tab shows who connected Quo, the Quo workspace, when it was connected, and whether Quo is connected for live updates: Active, or Not receiving. If the hookup is missing or Quo rejected it, the page explains that new texts and calls are not arriving. Owners and admins use Replace key from the connection menu to finish connecting or try again. It opens the same Connect Quo dialog; connecting again starts a fresh history import for the window you choose, and items already in Ariyel are not duplicated.
History import has its own status: queued, running, stalled, or failed. A failed import retries on its own; after repeated failures it stalls until someone retries it. Owners and admins can choose Retry import after a failure or stall. The import resumes from its saved progress within the history window chosen when connecting; a live connection alone does not mean history import has finished.
While history imports, a Syncing Quo notice shows the messages and calls imported so far, wherever you are in Ariyel. When the import finishes, it reads Synced Quo with the totals.
When a line is added in Quo after you connect, Ariyel picks it up at its next line check (every few minutes, or right away with Refresh lines) and imports that line’s history for the same window you chose when connecting.
What syncs#
After Quo is connected, open its Settings tab. Under What to bring in, switch each kind on or off. Switches save when you flip them—there is no Save button. If a write fails, the control rolls back and the error shows in that section. Only owners and admins can change these; for members the controls are disabled with the title Only an owner or admin can change workspace settings. Switching a kind off stops new ones from coming in; what is already imported stays. Each kind that is on appears on the record’s Messages tab and in Activity:
- Texts — in and out, including pictures.
- Calls — who called whom, how long, missed or answered.
- Voicemails — with Quo’s transcript when available.
- Recordings — audio never leaves Quo; open the call in Quo to listen.
- AI call summaries — Quo’s summary of each call on the record (needs Quo Business or higher).
- Full transcripts — off by default. Ariyel does not display a full call transcript on the record; open Quo to read it.
Under What the rest of the team can see (what the team sees of shared lines and of other people’s personal lines):
- Just who and when — they see that a call or text happened with a contact, and when. What was said stays with the people on the line.
- Everything — recommended. They can read texts, see call details and Quo’s AI summaries, and listen to voicemails on any record.
This is the workspace default, and new connections start on Everything. Shared lines always follow it, for everyone: under Just who and when, nobody reads a shared line’s texts, call details, or voicemails. Members can override it for their own personal line; the person on a personal line always sees all of it. Being a workspace owner or admin does not by itself reveal private line content.
A call or text from a number that isn’t on any contact always creates a new contact with the number filled in, so you can add the name later.
Ariyel files each call or text on the contact whose Phone ends in the same last 10 digits (the oldest such contact if several match), and on that contact’s most recently created deal.
Lines#
Under Apps → Quo → Settings → Lines, owners and admins can choose Refresh lines to refresh the Quo assignments. Ariyel also checks Quo for line changes every few minutes; lines removed in Quo drop off the list. Each row shows the number, the line’s name, whether it is Personal or Shared, who is on it In Quo, and who that is In Ariyel.
Ariyel matches each personal line to its person by email. Owners and admins check each match and use the menu in the In Ariyel column to choose the right member, or Unassigned to clear it. Status reads Matched or Needs a person. A shared line belongs to the whole team and nobody is matched to it: In Quo shows how many people are on it (such as 3 people), In Ariyel shows Whole team, and Status reads Ready. Matches set by hand are kept when lines refresh; a member who leaves the workspace is unmatched. An unmatched person does not receive private access through that line. Members see who is matched only on their own lines.
Your phone lines#
Open Settings → Personal → Phone lines to see your active personal lines and every shared line. Phone lines appears in Settings once Quo is connected. Each row identifies the line as personal or shared (Shared with the whole team · Follows the workspace setting) and shows what the team can see: Team sees everything or Team sees who and when. Choose Options to open a line. If no lines appear, check your assignment in Quo and ask an owner or admin to refresh and check the member match. A line removed in Quo, or one you are no longer on, opens as That line is no longer available; go back to Phone lines.
Open a personal line’s General tab and choose Everything or Just who and when. Only the person matched to the line can change it. The caption reads Using the workspace default: … or Using this line’s setting: …. Choose Use workspace default to remove an override. Changes save immediately; a refused save shows an error and restores the previous setting.
A shared line belongs to the whole team, so every member can open it. Its General tab shows the workspace setting; owners and admins change it under Apps → Quo → Settings.
Numbers that should not be logged#
Open a line’s Blocklist tab to see Never log these numbers. On your personal line, add a phone number or remove an existing entry: type the number and choose Add (on an empty list, choose Block a number first), or use an entry’s remove button. Add says Enter a valid phone number. for input that isn’t a phone number, and That number is already on this list. for a duplicate. Enter a 10-digit North American number (a leading 1 is fine) or an international number starting with + and its country code. Owners and admins manage a shared line’s blocklist from the line’s Blocklist button under Apps → Quo → Settings → Lines. Members see that Blocklist control on every shared line and can read the list there. Long lists offer Load more.
A blocked number is excluded from future calls and texts imported into Ariyel from that line, including history imports, before a new contact is created. Already imported history stays. Removing a number permits future logging; it does not automatically restore skipped history. A later eligible history import may bring that history in. This blocklist controls Ariyel logging, not whether someone can call or text you in Quo. A blocked number also never starts a Quo workflow from that line, and Send a text skips it when sending from that line.
On contacts and deals#
Contact and deal records show a Messages tab for texts, calls, and voicemails, with date dividers and a line filter. It opens at the newest message. An empty tab reads No messages yet; if it can’t load, it shows Failed to load messages from Quo. with Try again. A deal’s Messages tab also includes its contact’s texts and calls. Imported history stays on the record after you disconnect, with the note Quo is disconnected. History already imported stays here. While disconnected, Reply in Quo is unavailable. Once Quo is connected, Reply in Quo opens the newest conversation you are allowed to view, or the Quo inbox if no conversation link is available.
On Overview, a Messages section shows the five most recent texts and calls, and contacts get a Last contact highlight (for example Today · text).
The same line privacy applies in Messages, Activity, and Overview. Private items show who and when without message bodies, voicemail transcripts, call summaries, recordings, or conversation links; they read Private to the people on that line. Visible items can offer View in Quo, View the call in Quo, or Listen in Quo. The record side panel uses the Quo mark on its Activity rows; choosing a Quo row’s text opens the full record’s Messages tab.
Outbound texts show delivery as Delivered, Failed, or Not delivered; other states show as Quo reports them. Hover a failed tag to see the carrier code when Quo provides one. The tag Failed · opted out appears only when the contact’s Text consent is opted out. An unanswered outbound call reads Outgoing call · no answer (not Missed call); an inbound call nobody picked up is still Missed call. On Activity, that unanswered outbound card title is No answer. Long threads offer Show earlier messages; earlier messages you load stay in place when the thread refreshes.
Activity shows events such as Quo logged a call, Quo logged a text, or Quo logged a voicemail. When visible AI summaries are synced, the call card can include AI call summary · Quo. The Activity feed’s Messages and Calls filters remain available with retained Quo history.
Connecting Quo adds a built-in Text consent field to contacts. In Record details and the Overview highlight it shows Yes · source, date in plain words—never the stored code. Sources read Texted START (they texted START or UNSTOP), Set by hand (someone set it in Ariyel), Texted STOP, or Other source. For example Yes · Texted START, Sep 11 or Yes · Set by hand, Sep 11. Opted out shows Opted out · date, or the field is blank. You can edit it on the Contacts table, one contact at a time, and in Record details.
While Texts is on, a contact who texts STOP (or STOPALL, UNSUBSCRIBE, CANCEL, END, or QUIT) to one of your lines is set to Opted out, and their Messages tab shows a red opt-out banner. That starts Contact opted out workflows, not Text received. Texting START or UNSTOP sets them back to Yes. A workflow’s Send a text only texts contacts whose Text consent is Yes; see Workflows.
Disconnect#
Choose Disconnect on the connected Quo page in Settings → Apps, then confirm Disconnect Quo. Only owners and admins can disconnect. Disconnecting turns texting off for the workspace; connecting turns it back on. New logging stops and any history import in progress ends. Reply in Quo leaves records, Quo workflow triggers and actions leave the pickers, and Messages notes read Quo is disconnected. History already imported stays here. Imported texts and calls stay on your records and keep their privacy rules. Those changes show right away, without reloading the page. Personal phone-line settings require an active connection; saved line settings and history are retained for reconnecting.
Live Quo workflows stay on after disconnect: their Quo triggers get no events, and Send a text is skipped with Texting is not enabled for this workspace; other blocks still run. You cannot publish or switch a Quo-block workflow ON while texting is off, but you can still switch a live one OFF. Reconnecting resumes texts without re-publishing—see Workflows.
To reconnect, open Quo in Settings → Apps and connect again with a key. Your settings are kept, and history is imported again for the window you choose.