Notes — internal, team only

Internal only — the merchant never sees these. They ride along with the account, so the next rep picking it up has the context.

Files

Demo build: files up to 300 KB are stored right in the browser so View works; bigger ones are kept as reference entries only. Production: real object storage with per-account folders, previews, and access control.

Locations

Locations are managed here in Super Admin only — the first is created with the account, additional ones from this tab. The business admin sees them read-only.

Promo suggestion schedule

On each interval the system drafts the suggestions from this account's numbers. The batch queues on the Promotions tab the day before the send for review and approval.

Danger zone

Deleting deactivates the account immediately: surfaces go offline, scheduled sends stop, and data is retained (exportable) for 90 days before purge. Outstanding gift-card liability must be settled first.

Live numbers — read from this browser's shared demo data

Detail — computed from the live order & member ledgers

Same shared demo data the merchant's own dashboard reads, refreshed on every storage event. Fleet-wide analytics stay static fiction until a backend exists.

Services in use

Loyalty, ordering, gift cards, and kiosk read live from the tenant's published settings. Processing and Website are manual selections — click either chip to toggle it for this account.

Communications — merchant ↔ Splango

Inbound mail to support@splango.com and texts to the Splango number are matched to this account by the sender (owner & staff contacts on file; unmatched → triage queue). Replies from this box send through the shared support address with threading tokens — reply from the console and the log writes itself.

Promo suggestion service

Enrolled · Email · every week · 3 suggestions per send — channel follows the business's preferred contact. Change schedule · Promo Suggestions screen →

Business called wanting options on short notice? + New batch opens the campaign builder in rep mode — every scenario lands back here as a suggestion for review, then goes to the merchant for approval.

Each batch is drafted by the system on the account's schedule and lands here the day before its send for the success manager to review, edit, and approve. Sending delivers it by the account's preferred channel with a link for the merchant to approve, suggest edits, or request a call — the send and everything after lives in the comms log.