Results numbers
Results numbers bring into the client’s page the counts you look at today in GoHighLevel dashboards: how many leads with a given tag, how many appointments booked or showed. You define them once: together the numbers are the agency’s model, a single one, which applies to every client with a connected GoHighLevel sub-account. Each client sees the numbers calculated on their own data, in the Results tab.
Results numbers are included from the Professional plan up. They need the GoHighLevel app connected (Admin › Integrations › Calendars › GoHighLevel) and, for each client, their sub-account connected.
Where to set them up
In Admin › Integrations › Calendars, card Results numbers. Only admins see the card; the Results tab is visible to the whole team that can see the client. You can prepare the model before connecting the app too: the card tells you, and the tab uses it as soon as the app is connected.
Building the model
The card is the model editor: all the numbers are in the list and you edit them together, in place. Nothing is saved until you press Save model at the bottom of the card.
- Press Add number (up to 12) and give it a name (up to 60 characters), for example “Direct leads”. The number’s Calculation panel opens.
- Choose the source: Contacts (counts the sub-account’s contacts, by creation date) or Appointments (counts calendar appointments). For appointments you then choose what to count (see What to count in appointments).
- Add the conditions on the contact’s tags: with All of these tags the contact must have all of them, with At least one of these one is enough, with None of these they must have none of them. With no tags, for contacts, it counts all the sub-account’s contacts. Type the tag and press Enter (or the comma); tags are saved in lowercase, the way GoHighLevel saves them. For suggestions, choose a client: the card reads the tags of their sub-account and offers them while you type.
- For appointments you can also restrict the calendars (GHL calendar id; empty = all). For appointments, tags apply to the contact who booked.
- Choose the period. Repeat for the other numbers, then press Save model.
Each row of the list shows the name, the Visible switch (off, the number stays in the model but does not appear in the tab), source, period and a summary of the calculation; Calculation opens or closes the panel with the fields. The arrows change the order in which the numbers appear in the tab, Remove takes the number out of the model. New numbers are labelled New, those with a changed calculation Calculation changed. If a field is not valid, on saving the row is marked in red and the error shows under the field.
Discard changes takes the list back to how it is saved. If you close or reload the page with unsaved changes, the browser warns you. If you go to another page of the app instead, the draft is kept in this browser tab: back on the card you find it again with the notice An unsaved draft was restored, and you choose Keep or Discard. If the model was saved in the meantime (for example by another admin), the draft is discarded and the card tells you so. Every save ends up in the Activity log.
What to count in appointments
GoHighLevel keeps one status per appointment, the current one, and many clients never mark “showed” or “no-show”. That is why in an appointments number you don’t pick statuses by hand but what to count: each type decides the date that counts and the statuses that are included.
| Type | Date that counts | Statuses that count | Notes |
|---|---|---|---|
| Booked | The day the appointment was booked | All | Even if later cancelled or invalid, and even if they start much later (up to a year after the end of the period). |
| Upcoming | Start | New, confirmed | Only those starting from now to the natural end of the chosen period: the contract expiry (pauses included), the end of the trial, the last day of the month, the next 30 days (with “Last 30 days”) or the end of the range; for a “Since the start” number, everything upcoming in the next 400 days. The card says so (“From today to…”). Always calculated live: no history and no comparison with the previous period. |
| Completed | Start | New, confirmed, showed | Only those already past. Those never marked count as completed; cancelled and no-shows don’t. |
| Showed | Start | Showed | |
| No-show | Start | No-show | |
| Cancelled | Start | Cancelled | GoHighLevel doesn’t say when it was cancelled: the day the appointment was due to start counts. |
A lead books an appointment on 3 October for 10 October and cancels it on the 7th. For October it counts 1 among Booked (on the 3rd, the day it was booked) and 1 among Cancelled (on the 10th, the day it was due to start); it doesn’t count among Completed. Until the 7th, while it was still confirmed, it also counted among the Upcoming of “This month” (the 10th falls before the end of October).
Statuses marked late (for example a “no-show” set the day after) reach the numbers with the nightly update, which recalculates the last 30 days.
Saving the model: 3 saves a month
The model has 3 saves a month, which reset by themselves on the 1st of every month (in the agency’s time zone): unused saves do not carry over to the next month. A save uses one whenever it adds a number, removes one or changes the calculation of one (source, what to count, tags, calendars or period), even if you change several numbers at once: that is why it pays to build the whole model and save it once. At the bottom of the card a line tells you whether the changes in progress will use a save; the Saves this month counter (out of 3) is above the list.
Before a save that uses one, SalesControl asks “Is this the final version?” and tells you how many saves you have left and how many numbers will be rebuilt: only new numbers or numbers with a changed calculation start over with a new history, the others keep theirs. A removed number disappears from the tab with its history.
The name, the order and the visibility can be changed whenever you like, without using a save.
Once this month’s 3 saves are used, the calculation fields stay visible but locked, and Add number and Remove are disabled until the 1st of next month; name, order and visibility can still be changed. If you cannot wait for next month, write to SalesControl support, who can reset them.
If another admin saves the model while you are editing it, on saving the card asks you to reload: you see the current version and redo your changes.
The numbers’ history
Every number has a history stored in SalesControl, one total per day and per client:
- when you add a number, change its calculation or connect a client’s sub-account, SalesControl rebuilds the last 400 days in the background. While it works, the number’s card shows “History being built” with the percentage, and the number is calculated live as before;
- every night, after 02:00 in the agency’s time zone, the history updates by itself (the last 30 days are recalculated, so they follow the current tags; older days stay as they are);
- today is always calculated live: the tab adds the history up to yesterday and today.
The history keeps growing over time, beyond the 400 days GoHighLevel keeps for appointments. It is also rebuilt from scratch when the client’s sub-account or the agency’s time zone changes. If the sub-account is paused, the card shows “History paused” and resumes by itself: right away if SalesControl reactivates it, otherwise within 14 days of it becoming active again; “History unavailable” means SalesControl cannot build it (GoHighLevel does not answer, the app must be reconnected or the number must be fixed) and tries again every night for a week.
The period
- Follows the period filter: the number is calculated on the period chosen in the tab (current contract, trial, this month, last 30 days or a range) and compared with the previous period of the same length.
- Since the client’s start, no comparison: counts the sub-account’s whole history (contacts with no date limit, appointments from 400 days before the connection, plus the history that builds up), whatever period is chosen: useful when the agency connects SalesControl after the client has been active for a while.
Days are counted in the agency’s time zone, from 00:00 on the first day to 23:59 on the last.
The Results tab
In the client’s page, Results tab (only for clients with a connected sub-account), each visible number of the model becomes a card with the period value, the difference from the previous period, the growth chart and, for contacts, the all-time total. Details reads from GoHighLevel, right then, the list of contacts or appointments of the chosen period, with CSV export. Refresh recalculates today straight away, at most once a minute. How to read it, and why a number can differ from GHL, is explained in The Results tab.
Limits
- At most 12 numbers in the model, visible or hidden: once you reach 12, “Add number” is disabled until you remove one.
- 3 model saves a month that add, remove or change the calculation of numbers (see above); they reset on the 1st of the month, or earlier on request to SalesControl support. There is no longer a creations limit.
- A period can last at most 400 days.
- Each tag list takes at most 20 tags, the calendar list 50 calendars.
- Today’s part stays cached for 10 minutes: within that time you see the same calculation, Refresh redoes it.
- If the client’s sub-account is paused in GoHighLevel, the numbers cannot be read: the tab says so, and they come back when the sub-account is reactivated.
- If the card says the GoHighLevel app must be reconnected to read tags, press Reconnect in the GoHighLevel card: the app asked for a new permission.