Conversations (Quo Integration)

Conversations brings customer texts, incoming and outgoing calls, and missed calls from Quo into BlueSuite. Your team can follow up in one place, connect an inquiry to the right job or request, and review what happened when a customer contacts you again.

Connect Quo

The Quo integration is available on BlueSuite Advanced and Enterprise plans. You also need a Quo account with API access and the business numbers you want to connect. Calls are made and answered through Quo; BlueSuite displays their history and any available transcripts.

  1. An Owner or Admin opens Integrations → Quo and turns on Enable Quo.
  2. In Quo, create an API key for BlueSuite under your workspace’s API settings. Paste it into BlueSuite to check the key and load your available numbers.
  3. Select the business numbers to connect. Assign each number to a teammate or leave it shared, then save.
  4. Check the connection status before relying on incoming updates. If BlueSuite reports that setup is incomplete, contact support.

A number’s assignee is the default assignee for incoming conversations. You can assign an individual conversation separately without changing who owns the business number. Assignments help direct follow-up and determine which team members can access the conversation.

To bring in earlier activity, use Import texts and calls in Quo settings. Choose a connected number and import texts and calls separately, continuing through additional batches when available. Imports do not send customer messages or place calls. Group messages and calls that cannot be matched to a single customer may not appear in a customer conversation.

Start a customer text

Choose New text in Conversations. Select a contact and one of their saved phone numbers, or enter a custom number. Choose the business number to send from, add your message, and send. If only one eligible business number is available, it is selected for you.

A new outbound text needs a matching contact with recorded SMS permission for that number. If you can edit the contact, the form lets you confirm the customer’s permission and save it when sending. Otherwise, ask a teammate who can edit the contact to record consent. Entering a custom number or receiving a phone call does not establish SMS permission. Existing inbound text conversations can receive replies, subject to customer opt-outs and sending restrictions.

You can also choose Text customer from a contact, request, or job. The form uses that record’s customer and work context, so you do not need to select them again. See SMS Text Notifications for more about customer texting requirements.

Choose which inquiry the message belongs to

Texts and calls between the same customer phone number and business number stay in one conversation while it is open. This keeps an ongoing inquiry together, even when it includes both calls and texts. A different customer phone number or business number has its own conversation history.

If an open conversation already exists, New text defaults to Continue conversation. Its existing job and request links are kept. If it has no linked job or request, you can add permitted work or leave it unlinked. Earlier texts keep their original work links.

For a separate inquiry, users with permission to close conversations can choose Close current and start new. The old history stays together, and the new conversation uses the work selected for the new text. For example, a customer’s completed repair and a new request months later can have separate conversations. There is only one open conversation for each customer-number and business-number pair.

If you start from a different job or request than the open conversation is linked to, start a new conversation rather than attaching that message to the wrong work. Members who cannot close conversations will need an office teammate to help.

Follow up on unread texts and missed calls

The conversation list’s activity icon shows whether the latest interaction was a received text, sent text, call, or missed call. A separate dot indicates unread texts or unseen missed calls. The navigation badge counts conversations needing that attention, not the total number of messages or calls.

Read status is personal. Opening a conversation marks its existing incoming texts as read and missed calls as seen for you, including older activity. Viewing an expanded conversation on a contact, request, or job also acknowledges it when that panel is visible. It does not mark the conversation read for other teammates, close it, or remove missed calls from its history.

Use the conversation filters to narrow the list by status or assignment. Open means the inquiry is still active; unread means there is activity you have not seen. A conversation can be open with nothing unread.

Keep customer context and team notes together

Link the matching contact and the request or job the inquiry concerns. A conversation has one linked request and one linked job, not a collection of unrelated jobs. If a customer has several jobs, use the job’s status, date, and price, when you have access to pricing, to identify the right one.

You can review and reply to conversations from the customer’s contact, request, or job as well as from Conversations. The timeline combines text bubbles and call cards. Calls can appear without a recording or transcript; transcripts and call summaries depend on what is available from Quo.

Use the conversation’s assignee to hand off follow-up and internal notes to leave information for your team. Internal notes are not sent to the customer. The AI summary updates automatically as new activity arrives and can help you catch up, but check the original texts and transcripts before relying on details. Updates may take time and are subject to your workspace’s AI usage limit.

Close or separate finished inquiries

Close a conversation when its inquiry is finished. Its history remains available. The next new interaction starts a new conversation for that number pair without carrying over the previous job or request.

If a new inquiry has already been mixed into an older one, use End conversation here on the last text or call belonging to the old inquiry. That item stays in the closed conversation, and later activity moves into a separate conversation. Link the separate inquiry to its own work.

When more than one conversation exists for the same number pair, Conversation history lets you revisit the earlier inquiries. If you separated activity by mistake, Merge with previous conversation combines it again. Conflicting work links must be resolved before merging.

Control team access and notifications

Owners, Admins, and Managers have office-level conversation access. Members and Limited Members can access conversations assigned to them, subject to customer-contact visibility permissions. In Roles & Permissions, you can also allow those roles to view conversations on shared numbers or other teammates’ numbers. Viewing those conversations does not grant permission to manage the integration or close, split, reassign, or relink conversations.

Starting a text also depends on module permissions and access to customer phone numbers. Members and Limited Members send new texts from their own assigned connected numbers. Contacts access allows choosing a contact or entering a number. Without Contacts access, eligible users may still text the fixed customer from work they are allowed to access.

Teammates assigned a connected number can choose email and dashboard alerts for incoming texts and missed calls in their account notification settings. These alerts go to the eligible number assignee, not everyone who can view the conversation. Importing old history does not generate new incoming-message or missed-call alerts.

Use contact sync and automated texts

Optional Sync contacts to Quo copies BlueSuite customer names, company names, phone numbers, emails, and contact links to Quo. Existing contacts are queued when enabled, and later BlueSuite edits sync in the background. It is a one-way sync from BlueSuite. Contacts created separately in Quo stay separate, and turning sync off keeps contacts already copied.

You can separately enable Use Quo for automated texts and choose its sending number. Existing customer notification preferences and SMS permissions still apply. Quo texts use your Quo plan. Failed or unconfirmed texts are not automatically resent through another texting service.

For an On My Way notification, review the message, choose an arrival estimate if useful, and select SMS, email, or both. At least one channel must be selected. To customize the default notification wording, see Customize Email and SMS Notification Templates.

If something is not working

Turning off Quo and saving disconnects the integration from BlueSuite. Automated texts may still use BlueSuite’s built-in texting service according to your plan and notification settings, so review those settings if your intention is to stop customer text notifications.