Monthly recurring revenue
—— annual run ratePlatform command
Overview
Secure workspaceInternal admin
Guest communications
Keep your guests informed.
See what was sent, what needs attention and what each location has left in its allowance.
Open Communications to load messages.
Your channels
Needs attention
Allowances by location
Allowances stay with each location. Sending and billing locations are shown separately in the history.
| Location | Channel allowance | Used | Reserved | Remaining | Extra unit price |
|---|
Sending cost estimates
These are conservative estimates, not invoiced revenue. Provider costs use your configured rates. Currencies are kept separate; missing rates are not treated as zero.
Extra email pricing
Plan-specific selling prices in ZAR. Included allowances are unchanged. Packs contain 5,000 emails and do not expire. Prices are frozen when a send is queued or a purchase is quoted; previous transactions are not repriced.
Roll out included booking emails
Add booking-email allowances to existing public plans and active locations without changing membership prices, renewal dates or Paystack agreements. Each historical contract keeps its other features. Purchased packs cover extra emails; marketing email is unchanged.
Restaurant senders
Only verified sender domains can send as your restaurant. Otherwise your name appears via DotDine.
Set the name guests see
Email notifications
Choose what each location emails guests. Receipts include a private booking-management link. Emails use this location’s included allowance first, then purchased usage or approved extra usage at its plan’s price. Account security emails are not affected.
Booking message routes
Receipts and booking changes use email by default, subject to the settings above and a confirmed communication allowance. Choose a different route if needed. A fallback is used only when the first channel is unavailable.
Choose a booking message route
Send a guest update
Email guests who have given your restaurant marketing permission. This first release supports up to 100 guests per update. No message is sent while you prepare or preview it.
Create or update a message template
Request an estimate to see allowance and extra sending costs.
Your recent updates
Recent messages
| Sent to | Channel | Status | Sending location | Billing location | Units | Sent |
|---|
Spending limits
Owners can set a monthly limit and require approval for extra sending costs. No extra spending is allowed without confirmed rates and limits.
Set a spending limit
DotDine business command
Run the platform
with clarity.
Revenue, restaurant accounts, location memberships and customer operations in one decision-ready view.
Modelled contribution
——% contribution marginSubscribed locations
—— average monthly valueReservations today
—— expected coversActive restaurants—
Diner accounts—
Cost to serve—
Billing attention—
Provider links missing—
Six-month movement
Restaurant growth
Operator inbox
Needs a decision
- Billing attention
- —
- Failed onboarding
- —
- Payment reviews
- —
- Open support
- —
- Scheduled closures
- —
Restaurants and locations
Newest restaurant accounts
Restaurant registry
Restaurants
Each restaurant account is shown once, with its individual locations grouped beneath it. Locations can be hidden from diners without deleting their records.
| Restaurant account | Owner | Membership | Locations | Account state |
|---|
First impressions
Homepage hero
A dependable default photo, or a quiet shuffle of all published The Edit branches. Brand-level photos never appear in the slideshow.
Diner discovery
Locations, atmospheres & cuisines
Keep the choices restaurants use to describe each location consistent. Locations include a central map point and search radius.
Search areas
Locations
Room feeling
Atmospheres
Kitchen style
Cuisines
Onboarding control
Onboarding
The payment-to-schema lifecycle. Failed requests can only be retried when DotDine still holds a verified successful charge.
| Restaurant | Owner | Membership | Domain | Status | Updated |
|---|
Membership operations
Subscriptions
Every restaurant location has its own membership and commercial contract version. Preview proration before scheduling any change.
| Restaurant | Location | Owner | Plan version | Value | Status | Renewal |
|---|
Live entitlement ledger
Usage & limits
See what every location has consumed in the current period, where allowances are close to their limit, and the estimated cost to serve.
Allowance position
Location usage
Append-only ledger
Latest measured activity
| Restaurant | Location | Capability | Quantity | Source | When |
|---|
Commercial studio
Plans, value
& margins.
Build location memberships, price negotiated restaurant contracts and understand the cost of every entitlement before it is sold.
Membership portfolio
What DotDine sells
Published terms remain immutable. New pricing becomes a new version, so existing restaurants keep the contract they accepted.
Entitlement catalogue
What plans can include
Create measurable capabilities once, then assign limits independently to every public or private plan.
Unit economics
Know the cost before the price
Maintain immutable provider rates, then test revenue and contribution at the location volume you expect.
Select a plan and model revenue, cost to serve and contribution margin.
Financial operations
Revenue &
collections.
Invoices, credits, confirmed collections and Paystack processing health without exposing provider credentials.
Membership changes
Payment & collection checks
| Restaurant | Reference | New membership | Due now | State |
|---|
Billing ledger
Invoices
| Invoice | Restaurant | Period | Subtotal | Credits | Total | Status |
|---|
Account adjustments
Credit ledger
| Reference | Restaurant | Amount | Reason | Operator | Issued |
|---|
Collection rail
Payment activity
| Reference | Restaurant | Owner | Plan | Amount | Status | Updated |
|---|
Global Passport
Diners
Global customer relationships, saved restaurants and public reservation activity.
| Diner | Contact | Reservations | Saved | Restaurants owned | Joined |
|---|
Platform booking index
Reservations
Diner-visible reservation projections from every tenant, safely indexed in the public schema.
| Restaurant | Guest | Date | Party | Deposit | Status |
|---|
Customer care
Support
Operator-owned cases alongside active concierge requests.
Case queue
Platform support
Private desk
Concierge queue
Private dining desk
Concierge
Review requests and match them to private spaces restaurants have shared with DotDine.
Requests
Find a private room
Inventory is private. Confirm the date, availability and final terms with the restaurant before proposing a booking.
Service assurance
System health
Non-invasive dependency checks. Provider credentials are never returned to the browser.
Live checks
Control plane
Safety posture
Restaurant account removal
Close safely, or remove immediately in an emergency.
The normal closure keeps a reversible review period. A super administrator can also permanently delete a restaurant or one location immediately after entering a detailed reason, exact target phrase and current password. Any Paystack membership that may still charge must be cancelled first. Billing and audit history remains available.
Checking deletion guardLumosoft access
Platform team
Platform roles are separate from restaurant staff and always constrained to the public control plane.
| Operator | Role | Access | MFA policy | Last login |
|---|
Governance record
Audit trail
Who changed what, when, why, and the relevant before-and-after state.