Connecting Quo to LactaSite
Quo handles your texts and calls. Once you connect your Quo account, LactaSite keeps each patient’s communication log up to date automatically — no manual copy-and-paste, and recordings and transcripts come along for the ride.
What you’ll need
- An active Quo account.
- Permission in Quo to generate an API key (typically the account owner or an admin).
- About five minutes.
Step 1 — Generate an API key in Quo
Sign in to Quo and open your account settings. Find the “API keys” (or “Developer”) section, then create a new key. Give it a name like LactaSite so you can recognize it later.
Copy the key the moment Quo shows it — for security, Quo will not display the full key again. If you lose it, you can always revoke the old key and generate a new one.
Step 2 — Paste the key into LactaSite
In LactaSite, open Settings › My communications (or, if you’re an admin connecting on a consultant’s behalf, Company › Consultants › that consultant › Communications). You’ll see a short two-step flow that walks you through pasting the key.
Paste the API key you copied from Quo and press Connect. LactaSite verifies the key with Quo immediately. If your Quo workspace has more than one phone number, you’ll then pick which one is yours — LactaSite only syncs that number’s history, so two consultants sharing a workspace each pull just their own messages and calls. With a single number, that step is automatic. If the key is good, you’ll land on the connected view that shows the last four characters, your number, and your sync status. If something’s off, see Troubleshooting below.
Step 3 — First sync
The first time you connect, LactaSite pulls in your recent Quo messages and calls and matches them to existing patients by phone number. Subsequent syncs are incremental and run automatically as new messages and calls happen on Quo’s side.
You can press Sync now at any time from the connected view to fetch the latest activity on demand.
Troubleshooting
“Quo rejected that API key (401 Unauthorized).”
The key is either mistyped, has been revoked, or doesn’t have permission to read phone numbers. Double-check the value you pasted — an extra space at the start or end is the most common culprit — or generate a fresh key in Quo and try again.
“Quo returned an error (status …).”
Quo answered, but with something other than success. This usually means a temporary problem on Quo’s side. Wait a minute and try again; if it persists, check Quo’s status page.
“Couldn’t reach Quo to verify the key.”
LactaSite couldn’t connect to Quo at all. This is almost always a transient network hiccup. If retrying doesn’t help, contact us.
Messages aren’t showing up on a patient
LactaSite matches Quo activity to a patient by phone number. If a patient’s record is missing the phone number Quo is using, add it on the patient and run Sync now.
A note on privacy
Your Quo API key is encrypted at rest in LactaSite. Only the last four characters are ever displayed back to you, and the key never appears in logs. Synced messages and calls are stored under the same HIPAA-compliant safeguards that apply to the rest of your patient records.