Skip to main content
Belcenter AIHelp center
Monitor conversations

Campaign counters and sharing

Configure collection by centre, understand the figures and voluntarily share revocable aggregates.

The calendar always uses Brussels time, regardless of your account or browser time zone. Choose the date and time, then click Apply for each boundary. If another field contains an error, your selected dates are retained. A sharing expiry date works in the same way.

Confirmation must be the caller’s first reply after that recap, with no other dialogue turn. A refusal, an ambiguous answer or an intervening exchange invalidates that preparation; the bot must recap the wish again and prepare a new confirmation. Once the confirmation request is ready, the bot waits silently for this reply. After an explicit yes, the bot records the wish before continuing. A brief acknowledgement immediately after that answer preserves its validity.

Calls are grouped by their observed arrival day; wishes by their confirmation day. An interruption after a valid confirmation preserves the wish. Public JSON contains only the two published counters, scope and dates: technical totals and test, announcement, refusal and redirect categories remain authenticated.

Open Counters and sharing, then Create a campaign. You must be allowed to edit every selected bot; they must belong to the same organisation. Reading requires current access to every bot, including tag restrictions. Moving a bot to another organisation makes its old share inaccessible.

Enter a public campaign name, centres and bots, an inclusive start and an exclusive end in Europe/Brussels. Each bot belongs to one centre per campaign. Limits: 20 centres, 100 bots and 370 days. Use centre names, never personal data. An ambiguous repeated seasonal hour requires an explicit offset through the API.

The single Save at the top right launches collection. The save dock appears only for changes; a validation error preserves entered fields. Collection starts at that save, even if the requested start is earlier. No historical wishes are inferred from transcripts, summaries or call length. Scope and call definition are frozen; create another campaign to change them.

Understand the counters

  • Observed technical total: inbound phone calls actually recorded after launch within the period, deduplicated by source identity. Tests, announcements and refusals remain distinct.
  • Conversational calls: calls admitted to conversation, excluding tests, simulations, announcement-only calls and refusals. This does not prove a useful exchange or a wish.
  • Calls including announcements: explicit publication option including observed announcements, still excluding tests and refusals. The prudent default is Conversational calls.
  • Confirmed wishes: at most one per conversation and campaign after actual collection, a spoken recap and a new explicit affirmative answer. Runtime tools record structured evidence. Keywords, silence, an adult without a wish, an announcement, refusal or time-limit ending never suffice.

The bot prepares after recapping and asking for confirmation, then confirms after the new caller answer. Messages must already be persisted. Negative, ambiguous or qualified replies do not count; the initial version deliberately supports a limited set of affirmative phrases. The private journal keeps message references without copying the wish.

Changing a wish, replaying an event or several children in one call never adds another increment. A callback is another conversation: these figures never count unique children. Off-platform calls and unreceived events remain unknown. V1 covers inbound phone calls, excluding chats and outbound campaigns.

Share voluntarily

Before publishing, choose at least one counter from published calls and confirmed wishes. Separately select the daily trend to make those details public; otherwise days are absent from the page and JSON. Set a title (100 characters maximum, without personal data), light or dark appearance and large-counter or dashboard format. These choices are frozen for that link. Omitted expiry uses the campaign end; sharing a completed campaign requires a future expiry.

To embed the display in a website or player, explicitly select “Allow embedding in an iframe” and copy the code shown with the link. Any page possessing that link can then embed only the selected aggregates, without a management API key or cookie. Without permission, embedding is blocked. Create another publication or replace the link to change choices; rotation preserves unchanged choices. Internal collection continues after a share is revoked or expires.

A campaign stays private until Create public link is selected with a future expiry within 370 days. This requires permission to edit all scoped bots. Copy the link immediately: it is shown only when created. Large counter, the small dashboard with daily trend and public JSON share the same aggregates without numbers, conversation details, names, ages, wish text or management secrets.

Anyone with the link can read it until expiry or revocation. Revoke stops further reads. Replace link revokes the old link before issuing a new one for the same frozen scope. Previously viewed or copied figures cannot be remotely erased.

Refresh is indicative every 15 seconds, with last update and Brussels calendar days. A failure displays Refresh unavailable, retaining the last confirmed figures when available instead of a false zero. Expired or revoked links return no figures. Each link permits 120 reads per minute.

Review and correct an observed event

An administrator allowed to edit every scoped bot can open “Journal and corrections”, select an actually observed event and exclude or reinclude it with a reason of 1 to 1000 characters, without personal data or wish text. Original evidence is retained; every state change appends an audit entry recording actor, date, reason and previous-state reference. The private history is paginated and never published.

Corrections cannot create an event or arbitrarily increase a total. Reinclusion preserves business exclusions for tests and announcements. Excluding a call also removes its wishes from aggregates without erasing their evidence; GUI/API/CSV and publications apply the same journal. A concurrent correction is reported before another confirmation, retaining the entered reason. Equivalent API resources are /{id}/events and /{id}/events/{eventType}/{sourceKey}/review, using excluded, reason and the current revision.

API and export

The same services and permissions apply to /api/v1/campaign-counters: create, read scope, /{id}/aggregate, /{id}/aggregate.csv, publish /{id}/shares, rotate and revoke. Lists have at most 25 campaigns per page. Authenticated CSV contains the same centre and daily figures. OpenAPI documents fields and examples. No management API manually creates a confirmed wish.

Documentation updated with the application