Meeting to finalize the plan for integrating CallRail into Adava Care's existing call infrastructure. The core problem: GoHighLevel captures inbound calls but cannot identify the marketing source (e.g., Google Ads vs. organic search). CallRail will be inserted as an attribution layer in front of the existing RingCentral numbers, preserving all current routing logic while adding source tracking.
Attendees:
- Mark Hope — Asymmetric
- Melissa Cusumano — Asymmetric
- Sebastian Gant — Asymmetric
- Kurosh Dejgosha — Adava Care
- K. Krause — Adava Care
CallRail as attribution layer, not a replacement. CallRail tracking numbers will sit in front of the existing RingCentral numbers. The current IVR menu, regional routing, and call-handling logic remain untouched.
Forward to Column D (RingCentral numbers) only. The shared spreadsheet's Column D contains the definitive forwarding targets — Adava Care's RingCentral numbers that route to the IVR menu and regional teams. Other columns (Google Ads call extensions, GoHighLevel numbers) are irrelevant to this setup.
Use Asymmetric's CallRail account for now. To accelerate setup, the integration will be built under Asymmetric's existing account. Billing ownership transfer to Adava Care is deferred.
Melissa and Sebastian to implement internally. No need to walk through the setup live with the client. An internal working session will handle implementation.
Marketing Source (Google Ads / Facebook / Website)
→ CallRail Tracking Number [attribution captured here]
→ RingCentral Number (Column D)
→ IVR Menu (move-in / job / house inquiry)
→ Cary (Milwaukee region)
→ Queue: Administrator + Nurse + Regional Director (Nita region)
Adava Care's current stack (GoHighLevel + RingCentral) tracks that a call happened but not how the caller arrived. Without source attribution, it's impossible to measure marketing ROI — e.g., whether a Google Ads campaign is generating move-in inquiries or just organic traffic is.
CallRail solves this via dynamic number insertion and source-level tracking, connecting each call to the session/channel that drove it.
| Owner | Action | Due |
|---|---|---|
| Melissa + Sebastian | Schedule internal working session to implement CallRail setup | ASAP |
| Melissa + Sebastian | Report integration status on Wednesday client call | Wednesday (next call) |
| Adava Care (deferred) | Resolve billing ownership for CallRail account | TBD |
On the decision to use Asymmetric's account for now:
Mark Hope: "I tell you what, Melissa, let's just drive on with it in our account for now, and we'll come back. We'll have to deal with it later."
On the core attribution problem:
Mark Hope: "You can't see where the call came from in terms of, was it a Google Ad call? You're just seeing that it's coming from the website... with CallRail, we're going to be able to connect that call to wherever they, however they got to the website."
On the forwarding target (Column D):
Mark Hope: "So for now, we're going to pay attention to that column there, column D. We're going to forward to that number, and we don't care about the other number."
Kurosh Dejgosha: "Those are directly to the menus. They're my numbers in RingCentral."
On keeping the existing routing intact:
Mark Hope: "We're just going to put CallRail in front of these numbers that you've got so we can get attribution, but they're not going to do anything other than just push the call straight through to the numbers that you have now."