The person who prepares a guest campaign does not automatically need permission to send it. For most restaurants, a practical starting point is to let a marketing employee draft the message, have an owner or manager approve it, and give sending permission only to the person responsible for the final release. Limit audience exports to someone who has a specific reason to handle guest data.
That division can change with your team and service hours. A single-location owner may approve and send every campaign. A multi-location group may need a central approver and a backup who can act when that person is off. The buying question is whether the software can support the workflow you actually need without giving every staff member broad access.
Choose an owner for each campaign decision
Start with one named campaign owner. This person keeps the offer, audience, timing and final message together, even if other people perform individual steps. Without an owner, a draft can sit unapproved, or two managers can each assume the other has checked it.
Then decide who can make four distinct decisions: take guest data out of the system, prepare a draft, approve the draft and release the campaign. Approval means checking that the message is ready. Sending is the action that puts it into the delivery queue or otherwise releases it. Those permissions may be separate in a product, combined, or managed outside it. Ask the vendor to show you.
Consider what happens during a busy shift. If the only approver is usually on the floor at dinner, a campaign scheduled for that window may need approval earlier. If a manager can approve but cannot send, identify a sender who is available afterward. For a small team, the same trusted person may approve and send, but someone should still check the audience and offer before release.
Access to contact information is also different from permission to market to a guest. Ask how the product represents a guest's marketing choices and how staff can check the intended audience before sending. Do not assume that someone who can see a phone number or email address should be able to use it for a campaign.
Build a role matrix before comparing products
The following is a hypothetical setup for a single restaurant. The owner wants a coordinator to prepare campaigns, but does not want that person to export guest contacts or send a message without a manager's approval. The manager is the campaign owner and handles release. The owner is the backup approver and sender.
| Action | Coordinator | Manager | Owner |
|---|---|---|---|
| Export an audience | No | Only when needed | Yes |
| Draft a campaign | Yes | Yes | Yes |
| Approve the final version | No | Yes | Backup |
| Send or schedule release | No | After approval | Backup after approval |
The table describes the restaurant's desired policy, not a promise about any product. “Only when needed” should mean a named business purpose and a defined recipient for the file, not a standing invitation to download the guest list. Ask whether the system can restrict exports independently of viewing or selecting an audience.
For each draft, the coordinator records the offer, intended audience, channel and proposed send time. The manager checks those details against the actual message and approves the final version. If the offer, audience or timing changes afterward, the coordinator asks for another approval before release. Agree in advance on who can cancel a scheduled campaign and what happens if the manager is unavailable.
The practical details matter. Can a draft-only user edit a campaign after approval? Can the sender change the audience at release? Can an approver see the same message and recipient criteria the sender sees? If the answer to any of these is unclear, demonstrate the exact sequence rather than relying on a role name such as “editor.”
Review your current campaigns alongside the matrix. If an offer involves points or a reward, the approver should also check its terms and who is eligible. Your loyalty setup and campaign audience may involve different decisions; a permission to draft a message should not automatically imply permission to change a reward.
Compare access approaches and their operating costs
Bring the matrix to each vendor and ask for a demonstration using the roles you intend to assign. Compare the following approaches against your staffing, guest impact and quote. A product may support one approach more readily than another; do not assume it provides a particular approval control.
One trusted user prepares and sends
This is simple to administer and can suit an owner-run restaurant with infrequent campaigns. It also puts the entire workload on one person and makes an independent check easy to skip. If that person is away, a campaign may wait or someone else may be given broader access than intended.
Ask how individual accounts are managed and whether a backup can have their own access. Consider the guest impact of an incorrect offer or audience, as well as the staff time needed to review each message.
Separate drafting, approval and sending
This approach gives a coordinator room to prepare work while keeping the release decision with a manager. It can reduce the chance of an unchecked draft reaching guests, provided the system actually blocks unauthorized sends and the team follows the review step. It also adds handoffs, so allow enough time for a manager to approve before the intended send window.
Ask whether approval is recorded in the product, whether it applies to the final audience and message, and whether changes invalidate it. Find out whether a scheduled send needs fresh approval after an edit. If the system combines approval and sending into one permission, decide whether that matches your policy.
Use a manual approval outside the product
If the product cannot enforce your preferred separation, the coordinator can prepare the copy outside the live campaign account and send it to the manager for review. The manager then creates or enters the approved version and releases it from an authorized account. Keep the approved copy and audience description together so the manager can compare them before sending.
This fallback adds staff work and relies on people following the procedure. It also may not prevent an authorized sender from changing the message or audience. If that risk is unacceptable, keep looking for a product that can enforce the control you need. Do not share a login to make the workflow easier; individual accounts make responsibility clearer.
Compare written quotes on the same basis. Include fixed subscription or account charges, variable message or usage charges, and any quoted setup, training or extra-user costs. Ask about exception costs too, such as a change to the configuration or help restoring access. A quoted messaging or processing fee alone is not the all-in operating cost. Staff review time is a separate operating consideration, even if it is not on the vendor invoice.
Check Fleksa's plans for current pricing; the plans page was checked in November 2026. Ask for a current quote and confirmation of the permissions and setup that apply to your account.
Run a safe permission test before selection
Use a simulated environment or a vendor-provided demonstration that cannot deliver a message to a real guest. Confirm the safety controls before anyone starts: no real payment, guest message or courier dispatch should result from the exercise. Use a fictional campaign, fictional contacts and a non-delivering send mechanism. If the vendor cannot provide a safe way to attempt release, use a walkthrough instead and record that the blocking behavior remains untested.
In this hypothetical test, the coordinator signs in as a draft-only user and prepares a fictional campaign. The manager has not approved it. The coordinator then attempts to send or schedule it through the simulation.
- Expected result: The attempt is blocked, or the campaign is held without release until an authorized manager approves the final version. The coordinator cannot approve it personally.
- Pass: The draft-only user cannot release the campaign, and the manager can identify what needs approval. After an authorized approval, the permitted sender can complete the simulated release.
- Fail: The coordinator can release the campaign without the required approval, or the approval does not cover the final message and audience under the restaurant's policy.
- Record: Note the account role, attempted action, displayed result, approval status and any change made after approval. Save a screenshot or written demonstration notes without real guest data.
Repeat the simulation with the manager absent. Can the owner act as backup without using the manager's account? Then change the draft or audience after approval and check whether the system requires another review. Also attempt an audience export as the coordinator. A blocked send is useful, but it does not answer whether guest data can be downloaded.
If the product fails the send test, the hypothetical restaurant's decision is to use the manual fallback only if the owner accepts its extra work and residual risk. The coordinator prepares copy outside the live account; the manager checks it and is the only person who enters and releases it. If the restaurant needs the software itself to enforce approval, a failed test is a reason not to select that setup.
A simulation checks permission behavior without contacting guests. A later live service pilot is a separate decision: use authorized staff and an approved campaign, with normal review and a plan to stop or correct it. Do not treat a practice send as a reason to contact real guests.
Next step: Fill in the role matrix with your staff names, identify your backup approver, and ask Fleksa to demonstrate the relevant controls in its restaurant marketing automation workflow. Compare the demonstration with your current process before assigning access.
Frequently asked questions
Can the same person approve and send a campaign?
Yes, if that fits your policy and the product's permissions. Decide who checks the final message and audience, and arrange a backup when that person is unavailable.
Should a campaign editor be able to export guest contacts?
Not necessarily. Drafting a message and downloading an audience serve different purposes. Grant export access only when the person's work requires it, and ask whether the product can restrict it separately.
What if the software cannot require approval before sending?
Keep draft preparation outside the live campaign account and have an authorized manager enter and send the approved version. If you need an enforced block rather than a manual procedure, consider another setup or product.
