Troy Method Dashboard — Setup Guide
Last updated: July 25, 2026
Troy Method Dashboard is a private HighLevel integration that keeps your operations dashboard in sync with every conversation in your HighLevel sub-account — staff replies, automated workflow messages, and inbound patient/lead messages — in one timeline.
What it does
- Subscribes to HighLevel's native conversation events (
InboundMessageandOutboundMessage) so every message is reflected in your dashboard — including messages sent by workflow automations that would otherwise never appear. - Read-only: it never sends messages or modifies anything in your HighLevel account.
- Each event is verified, de-duplicated, and added to the correct contact's thread, in order.
Requirements
- An active service relationship with Outcome Lab (the integration is private — it is not available for general installation).
- Admin access to the HighLevel sub-account (location) you want to connect.
Installation
- Step 1. Outcome Lab sends you the private install link for your sub-account.
- Step 2. Open the link while signed in to HighLevel, choose the correct sub-account, and click Authorize. The requested permissions are read-only conversation scopes.
- Step 3. That's it — allow a few minutes, then send or receive any message on that sub-account and it will appear in your dashboard thread.
Repeat once per sub-account. There is nothing to configure inside individual workflows.
Verifying it works
- Reply to any thread from a test contact (inbound), and trigger any automation that sends a message (outbound).
- Both should appear in the dashboard conversation view within seconds, correctly labeled.
Uninstalling
In HighLevel: Settings → Integrations → find Troy Method Dashboard → Uninstall. Event delivery for that location stops immediately. Data already synced remains in your dashboard record; see the Privacy Policy for deletion requests.
Troubleshooting
- No messages appearing: confirm the app shows as installed on the right sub-account, then contact support with the clinic name and a timestamp.
- Duplicate messages: shouldn't happen (events are de-duplicated) — if you see one, report it; it's a bug we want to know about.
Questions or a new sub-account to connect: [email protected].