Demonstration three
What revenue visibility
can look like.
An example of the kind of view a Managed Revenue Intelligence arrangement can include: where enquiries came from, whether they arrived, who owns them, what is overdue and whether the numbers agree. Example interface. Fictional records. No live customer information.
Example console · fictional business “Verdant Hill Retreat”
Enquiry to revenue, last 14 fictional days
14 fictional days, 6 to 19 October
Enquiries per day and delivery status
- Delivered to CRM
- Delivery failed
View as a table
| Day | Delivered | Failed | Total |
|---|---|---|---|
| 6 Oct | 5 | 0 | 5 |
| 7 Oct | 7 | 0 | 7 |
| 8 Oct | 6 | 1 | 7 |
| 9 Oct | 8 | 0 | 8 |
| 10 Oct | 9 | 0 | 9 |
| 11 Oct | 4 | 0 | 4 |
| 12 Oct | 3 | 0 | 3 |
| 13 Oct | 7 | 0 | 7 |
| 14 Oct | 6 | 2 | 8 |
| 15 Oct | 8 | 0 | 8 |
| 16 Oct | 7 | 0 | 7 |
| 17 Oct | 5 | 0 | 5 |
| 18 Oct | 3 | 0 | 3 |
| 19 Oct | 5 | 0 | 5 |
Unresolved exceptions (4)
X-118Form-to-CRM webhook returned 401 for two submissions (E-0431, E-0432).
Re-send both records; rotate the integration key.
X-119Follow-up overdue by more than 12 hours (E-0437).
Reply today or reassign.
X-120Source not captured on 3 of the last 20 enquiries (WhatsApp and phone).
Add tracked links to WhatsApp entry points; ask callers how they heard.
X-121Reconciliation: 2 bookings in the booking engine have no matching enquiry record.
Match by email and date; confirm the walk-in rule.
Reconciliation
- Last run
- 17 Oct
- Bookings without an enquiry record
- 2
- Enquiries with a known source
- 85%
- Marketing vs CRM totals
- Agree after 2 adjustments
Recent enquiries (12)
| ID | Channel | Source | Received | Delivered to CRM | Acknowledged | Follow-up | Status |
|---|---|---|---|---|---|---|---|
| E-0441 | Website form | Paid search · spring-retreat | 19 Oct 09:14 | Confirmed | 09:14 (automatic) | Reply sent 09:52 | Open |
| E-0440 | Not captured | 19 Oct 08:51 | Confirmed | 08:51 (automatic) | Due 19 Oct 12:00 | Open | |
| E-0439 | Booking engine | Direct | 18 Oct 17:30 | Confirmed | 17:31 (automatic) | Reply sent 18 Oct 18:05 | Qualified |
| E-0438 | Referral | 18 Oct 15:12 | Manual | 18 Oct 16:40 | Reply sent 18 Oct 16:40 | Qualified | |
| E-0437 | Website form | Organic search | 18 Oct 11:02 | Confirmed | 11:02 (automatic) | Overdue 20 h | Exception |
| E-0436 | Phone | Not captured | 17 Oct 14:20 | Manual | 17 Oct 14:20 | Quote sent 17 Oct | Qualified |
| E-0435 | Meta campaign · october-stay | 17 Oct 10:05 | Confirmed | 10:05 (automatic) | Booked 18 Oct | Booked | |
| E-0434 | Website form | Paid search · spring-retreat | 16 Oct 16:48 | Confirmed | 16:48 (automatic) | Declined 17 Oct | Declined |
| E-0433 | Booking engine | Organic search | 16 Oct 09:30 | Confirmed | 09:30 (automatic) | Booked 16 Oct | Booked |
| E-0432 | Website form | Newsletter | 14 Oct 13:15 | Failed | Not sent | Not started | Exception |
| E-0431 | Website form | Paid search · spring-retreat | 14 Oct 12:58 | Failed | Not sent | Not started | Exception |
| E-0430 | Not captured | 14 Oct 08:40 | Manual | 14 Oct 10:10 | Booked 15 Oct | Booked |
No fictional enquiries for this channel in the period.
Example interface. Fictional records. No live customer information. Numbers, dates, channels and exceptions are illustrative. A real engagement defines which measures matter, where the data comes from and who acts on each exception.
What this is,
and is not.
This is a technical demonstration with fictional records. It is not a deployed GoodCloud product, not a live client system, and not a promise that every engagement produces exactly this view.
In a real engagement the measures, data sources, refresh schedule, exception rules and the person who acts on each alert are agreed in writing. Monitoring and reporting are offered only where the operating arrangements can support them.
About Managed Revenue Intelligence