Import guests and review consent
Open Guests → Members → Import guests, or the available import entry in the
marketing workspace. For the authorised guest-data manager. Use a restaurant
export you are authorised to process; import only the fields needed.
Preview before writing
- Choose a CSV file or paste CSV text. Review Column mapping, including
name, email, mobile, tags, birthday, and Marketing opt-in. Ignore columns
that are irrelevant or should not be imported.
- Select Preview import. Dry run: nothing written yet lets you inspect
new guests, merged records, skipped rows, and sample rows.
- Check contact matches and conflicts. Correct the source before importing if
it would join different people or attach the wrong phone number.
- Select Import guests, read the create/merge/skip confirmation, and
confirm deliberately. Inspect the completion summary and resulting profiles.
Rows without usable email or mobile can be skipped. Invalid emails can be left
off imported records; correct them in the source rather than assuming all
imported guests are reachable. Inspect an existing import's result before
retrying; do not create duplicate manual profiles to bypass matching.
A profile in Members is not permission to market to it. Unclear consent signals
can leave imported contacts held from sends. The current Confirm marketing
consent flow requires an Evidence reference, Original consent date,
and Exact consent wording shown.
Confirm only when that evidence genuinely applies to every held contact in the
import. Use a durable evidence reference, not pasted guest personal records; the
date is the original instruction, not the import date. Do not use this
explicit-consent confirmation to assert an unverified soft opt-in or override an
opt-out. If evidence differs between people, separate and review the source
rather than making one blanket confirmation.
The release acknowledgement records explicit consent and preserves existing
opt-outs. TablePort recording it does not establish legal approval. For UK
lists, check the restaurant's evidence against the
ICO's electronic-mail marketing guidance.
Consent must identify the intended sender and contact method; buying or
importing a list does not create that permission.
If confirmation fails, preserve the hold and evidence rather than changing a
profile tag to force eligibility. See Consent. Escalate
with import reference, mapping, summary, hold/error, and evidence reference
through an authorised channel, keeping raw guest data out of public captures.