← Ranedo products

Guest database / Ranedo

Guest database remember more for the next visit.

Keep contact details, notes and relationship history together. Find a guest before arrival, review previous information and organise contacts with tags. Give your team better context when welcoming returning guests.

  • Profiles, notes and tags
  • Activity and linked orders
  • Channel-specific consent records

Choose the features and plan that suit your venue.

Guest database

Examples from your venue

  1. A regular books a table

    Continuity between employees.

  2. A returning customer

    More context for the conversation.

  3. An invitation to a new menu

    An organised database before sending.

Workflow illustration, not a screenshot of the application.

What changes for your venue?

Build shared knowledge about guests that your team can use on their next visit.

01

Profiles, notes and tags

Continuity between employees.

02

Activity and linked orders

More context for the conversation.

03

Channel-specific consent records

An organised database before sending.

Information the team can share

A profile combines contact details, notes and labels. Search and filters help locate the right person, so useful service information does not stay with just one employee.

Understand previous visits

Review activity and orders matched through contact details. Tags and VIP labels organise your database, while automatic segments help identify groups with similar histories.

Prepare contacts for communication

Review channel-specific consent, including its date and source. Connect the database with campaigns to choose recipients, or export CSV for further work outside the panel.

Start with a well-prepared setup.

Follow these four steps, then test a realistic scenario with your team.

  1. Review contacts

    Look at profiles created through guest service.

  2. Complete information

    Add useful notes and correct contact details.

  3. Organise the database

    Use tags, filters and VIP labels.

  4. Connect communication

    Check consent before preparing a campaign.

What should you prepare?

Define a simple note-taking policy, staff access and the purpose of using guest data. Record information needed for service and keep it current.

Before you start: common questions.

Before you decide, get answers to the key questions. If you would like to discuss your workflow, let’s talk.

Tell us about your venue →
Where do contacts come from?

The database connects with guest workflows including reservations. A booking can create a contact or complete an existing profile using the supplied details.

Does a profile require email?

No. Reservation contacts can exist without email. A phone number can help identify a guest when no email is available.

Can I see earlier orders?

Profiles show linked orders matched by email or, when email is absent, phone. Completeness depends on the details recorded with orders.

What are tags for?

They organise contacts around your needs. VIP labels and automatic segments provide additional ways to browse the database.

Can I export contacts?

Yes. CSV contact export is available according to user permissions.

Does having a contact mean marketing consent?

No. Contact details and consent are separate. Check permission for the chosen channel; a profile alone is not enough.

Build shared knowledge about guests that your team can use on their next visit.

Create an account or arrange a demo to explore how this feature can work in your venue.