Club Vero — The truth behind every visit
Reset your password
Enter the address you sign in with and we will send you a link.
Set your password
You're using a temporary password. Choose a new one to continue.
Club Vero — The truth behind every visit
Property
Loading…
Overview
Overview
Trends
Data
F&B
Staff
Golf
Pro Shop
Racquets
Events
Service Recap
Event Recap
Intelligence
AI Insights
Training Actions
Raised & Recognition
Case Alerts
Watchlist
Feedback
People
Members
Visits
Outreach
Communications
Survey Queue
Survey Log
Message Log
Setup
Upload
Survey Builder
Reports
Board Pack
Committee Pack
SMS Credit
Settings
Help & FAQ
Signed in as

Member Experience

Last 30 days
General Manager · Full Access
Automated pipeline — upload the end-of-shift report and Club Vero does the rest. No manual sending, no chasing.
Property NPS
—
Last 30 days
Response rate
—
Last 30 days
Surveys sent
—
Last 30 days
Open case alerts
—

Benchmarked indices

Last 30 days
Each index is scored 0–100 from the questions tagged to it in your survey templates. Questions you add without a tag are collected but never affect these numbers.
CHI · Club Health
—
Loyalty & recommendation
SSI · Service Satisfaction
—
Staff & service quality
OHI · Operational Health
—
Operational effectiveness

Outlets

By outlet, over the period above. Score is every rated answer on one 0–100 scale and is what the status band reads; NPS is beside it with the number who answered, because a single 9 out of 10 is +100.
Loading...

Recent open-text feedback

Feeds directly into the weekly AI analysis.
No comments yet.

Case alerts

Flagged the day they're received, not at month-end review.

Trends

Average score first — every rated answer on one 0–100 scale, so a middling reply moves it by its share of the replies. Then NPS, which does not behave like an average: one 9 out of 10 is +100, so each month says how many people answered. After those, the questions that survey actually asks: each line is named from its own template — an outlet that nominates its own survey is charted under its own questions, not the dining room's.
No trend data yet. Charts will appear once you have survey responses across multiple months.

Food & beverage

Dining scores from the surveys sent after a qualifying visit. Golf rounds are on their own screen; events are their own department.
Average score
--
F&B NPS
--
Response rate
--
Responses
--
Average scores
No data yet
Recent responses · last 5
No responses yet

Outlet performance

Every active outlet over the selected period. Click an outlet to read its own scores and comments above.
Trade
Loading…
By membership category

Recent F&B comments

Last 5 · feeds the weekly AI analysis
No comments yet.

Server leaderboard

Server scores from survey data. Composite = NPS (30%) + Service (30%) + Overall (20%) + Food (20%), each on 0-100. The board is ordered by composite score.

Staff shift feedback

What your team said about their own shifts — anonymously. Answers are stored with no link to the person who wrote them, arrive in shuffled order, and are held back entirely until enough have come in that no single one can be traced back. Set one up in Settings → Staff survey occasions.

AI analysis

to
AI-generated training recommendations and recognition, based on server survey scores and guest comments for the selected period. Each action is assigned on generation to whoever owns the outlet the server worked most, the same way a case alert is — set that in Settings → Outlets.

Weekly AI narrative

Generated weekly on Fridays from survey comments across all outlets. Click "Generate now" to run analysis on-demand.
Loading insights…

Training action plans

Generated weekly by AI from guest feedback. Priority-tagged, assigned to a person, tracked to completion.
All plans
Unassigned
Mine

Case alerts

Any response scoring low is flagged the same day it's received — not at month-end review. It is assigned and emailed straight away, and passed up if nobody resolves it inside the club's window — set both under Settings → Case alert rules.
All
Awaiting call-back
Open
Assigned
Resolved

Did the recovery work?

Every member who had a bad visit, and what happened the next time they came in.

Still owed a good visit

Longest wait first. A case marked resolved does not clear anyone from here — only their next visit does.

Settled

They came back and told us how it went. These are the ones the recovery rate is measured on.

Member health

Each member against their own rhythm, adjusted for how the rest of the club moved over the same weeks.
Loading
—
Worth a call, in order
MemberWas comingNowLast visitAt risk

Add a member

These are the fields the eligibility check and survey delivery use — same six as the CRM export.

Bulk import

Upload the club's membership export — matches the six required fields exactly.
⬆
Drop a CSV or PDF here, or click to browse
member_id, first_name, last_name, phone_number, email_address, communication_preference, opt_out_flag
Download CSV template →

Members

Member #NamePhoneEmailPrefStatus

Edit member

The quarter, as the board reads it

Everything below is what the PDF contains, in your club's branding.

What it will say first

The cover page, drawn from the numbers below.

What we said we would do

Plans the club chose to make, and cases it had to close. Kept apart.

Member issues

What happened next

What members are saying

Your club's branding

Two colours and a mark. Set nothing and packs come out in Vero's palette.
Cover and headings
Rules and marks
None chosen
PNG or JPEG, under 512KB
BOARD PACK
Your club

Not in this pack

What a reader would look for and will not find, with the reason.

For discussion

Most costly first.

Joined and left

Reasons for leaving

Usage

Measured against every member, including those who never visit.

Compared with the previous period

Share of members who used each outlet.

Consistency

Share of scored visits that scored poorly. Worst first.

Event return rate

Members at their first event who came to another.

Guests and introductions

Who introduced new members

Record an introduction

Only if you know who introduced them.

Record feedback

Something a member said without being asked. Complaints open a case.

Feedback page for members

Members can send feedback themselves. It arrives here, and complaints open a case.
Use this link on a QR code, in the newsletter or on the website. For a link that sends feedback under a member's own name, open their profile.

Repeated complaints

Different members complaining about the same thing.

All feedback

Not included in any score.

How it reached the club

Call list

Members your standing rules have found. Log each call: what they say goes on their profile.

New outreach

Choose a group, then untick anyone you don't want to contact. Nothing is sent until you approve it.

Left out

A starting point. Edit the questions on the draft.
Highest-value members first

Standing rules

Checked every day. A rule never sends anything: it adds members to the call list, or to a draft survey that waits for your approval.

New rule

days

Drafts and sent

Left out

Questions

Session

What was said

Comments, not scores. "Agreed" is how many people in the room agreed.

Results

Members contacted who visited again afterwards.

Log a call

Goes on their profile and into the Feedback inbox. It never affects a score.

Queued surveys

Loading…

Who will receive a survey

Everyone below qualified on spend and hasn't been surveyed at that outlet inside its re-survey window — or was, and never replied for long enough that they are askable again. Send someone early, or remove anyone who shouldn't get one.
DateNameOutletSpendChannelGoes to

Budget

Food and beverage budget against the recap and the POS. The month in progress is read against its budget so far.
Type a figure per month, or paste a column (or food and beverage side by side) straight out of a spreadsheet into the first box. Leave a box empty for no budget — that is different from a budget of $0.
The budget is not available to your account.

Who the takings come from

Every member’s spend across dining, golf and racquets. Guests and house accounts are left out.
to

By category

Per member divides by the whole roster; per active only by the members who spent or played. Click a category or a figure to narrow the screen to it.

Across every outlet

Darker is larger within its column. Click a cell or a heading to narrow the screen to it.

When

Spend bands

How many members spent how much, with what they spent beneath. Played, spent $0 used the course or the courts without anything going through a till.

What the kitchen sold

Attach is the share of checks carrying the item. Came back is the share of members who ordered it again after trying it. Click an item to see who orders it.

Members

Every transaction

Every visit, round, booking and check behind the figures above.

Add a visit

Log a visit manually — works for members, guests, commercial visitors, or anyone else.

Visit log

All visits on record — from POS uploads and manual entry.
All
Members
Visitors
Commercial
Golf
Other
DateNameTypeOutletSpendQualifiesSurvey

Events scorecard

Events carry their own NPS and CSAT. Every type you run is scored on its own and rolls up into Events overall — this is a separate department from the outlets, so none of it moves your Club Health, Service or Operational indices.

Event types

The kinds of event you run. Each one is scored on its own line of the scorecard above, and can nominate the survey its events ask.

Suggested events

From what members actually order — wine, whiskey, pizza, whatever this club's own checks say. A member counts towards an occasion once they have had something from it on three or more visits, so this is habits rather than one good night. The ones you have never run are listed first; every figure is a count of checks, and a theme too thin to fill a room is left out rather than softened.
Loading...

Create event

Leave the send date empty to send by hand from the event's own screen. Nothing goes out between 8pm and 8am — a blast scheduled inside those hours waits until the morning.

All events

DateEventTypeAttendeesSurveys sentResponsesNPSCSAT

0
Attendees
0
Surveys sent
0
Responses
—
NPS
—
CSAT

Service recap

The post-function report for this event — how it ran, what went on the bill, and who worked it. Saved against the event, so it is searchable next year when the same function comes round.
Function notes
Linens
Billing
Staffing
Name and hours worked. A name matching somebody on the Servers list is marked, and those are who a staff survey for this event can reach.

Recent responses

What attendees answered, newest first, under this event's own questions.
No responses yet

AI insight

Reads the scores and the written comments from this event and says how it went, what worked, and what to change next time.

Event setup

The type decides how this event is grouped on the scorecard. The template decides what attendees are asked — a golf event asks about the course, a dinner about the food.

Add attendees

Add members (by ID) and/or guests (by name + contact info). Both receive event surveys.
— or —
☰
Drop a CSV here
Must have a member_id column

Attendees

Member #NameChannelContactSurveyResponse

Survey log

Every survey sent, pending, and completed — with delivery channel and response status. Answers are shown against the question each member was actually asked. A survey that never went out is listed as Not eligible.
All
Awaiting reply
Answered
DateMemberOutletChannelStatusNPSOverallLink

Message log

Every SMS and email sent by the system — surveys and test messages.
All
SMS
Email
App push
Failed
DateMemberChannelRecipientStatusBody

Send survey manually

Close this case

Period report

Everything below is computed once on the server, so the download and the screen can never disagree.

Club indices

Each index is scored 0–100 from the questions tagged to it.

Month on month

Responses and NPS across the period.

By outlet

Server performance

Servers with at least three responses in the period.

NPS composition

The net score hides its own make-up: a club with few detractors and one with many of both can net to the same number, and they need different work.

Week by week

The same responses as above, cut finely enough to see when something changed.

Outlet trends

Each outlet over the same periods — whether a score has drifted or dropped.

Response rate

Of the surveys sent in this period, how many came back — by room, by week, by survey and by type of member. A survey belongs to the period it was sent in and counts as answered whenever the answer arrived, so a Friday send answered on Monday is a success rather than a miss.

Segments

Who the member was, and when they came in.

Question detail

Every question in every template answered this period — including ones you added yourself, which are collected and reported here even though they move no index.

Events

Scored separately from the outlets, and deliberately not part of the club indices.

Case alerts

What was done about the cases

Events the club ran

Balance
—
Roughly buys
—
more text messages
Automatic top-up
—

Top up

Credit is used as messages go out. When it runs out, text sending stops until it is topped up — nothing is lost, and the next send picks up whoever was missed.
$
Payment is taken by Stripe on their own secure page. Card details never reach this dashboard or our servers.

Automatic top-up

Keeps surveys sending without anyone having to watch the balance. When credit falls below the trigger, the saved card is charged for the top-up amount.
$
$
$

Payments

Every top-up, refund and adjustment, newest first.
DateTypeAmountBalance afterNote

Daily spend

What credit is going out per day. A flat stretch means nothing was sent; a spike is usually an event blast.

What credit was used on

Messages sent, by day and type. A day's surveys are grouped into one line rather than listed individually.
DateTypeMessagesCost

Send survey manually

Automatic imports

Schedule the POS to email its end-of-shift report here every night and nobody has to remember to upload it. Each report becomes the night's visits, exactly as an upload does. The same night arriving twice — a resend, a forward, a re-run — is only ever imported once.
The last 14 nights
Everything that arrived

Upload end-of-shift report

One file, once a day. Everything after this happens automatically. The day's golf tee sheet goes up on Golf — same job, other file.
⬆
Drop your POS export here, or click to browse
PDF, CSV or Excel · NorthStar, Jonas, Lightspeed and Club V1 exports are read as they come out of the POS
Eligibility logic applied automatically: a visit qualifies for a survey if its spend meets the outlet's threshold and the member hasn't already been surveyed for that outlet within the frequency window. Everything else is skipped — no manager review needed.
Processing…
MemberOutletSpendQualifiesReason

Golf surveys

Course conditions, pace of play, and pro shop scores from post-round surveys sent via tee sheet upload.
Average score
--
Golf NPS
--
Response rate
--
Responses
--
Average scores
No data yet
Recent responses · last 5
No responses yet
By membership category

Golf & dining crossover

Measured in member-days, so somebody who ate twice after one round counts once.
Loading
—
Stayed to eat, by day
Where golfers eat
Regulars who never stay

Upload tee sheet

Upload the day's tee sheet. The system extracts member IDs and names so you can review who will receive the golf survey before sending.
⛳
Drop a tee sheet here, or click to browse
PDF, CSV, or Excel (.xlsx) with member IDs or names · date is auto-detected
Processing...

Golf survey log

All golf surveys sent, showing member, date, and completion status. A round that never became a survey is listed as Not eligible.
Loading...

Survey sent after a round

The questions members see after their round live in Survey Builder, with every other survey the club sends.
Loading…

The shop’s till

Upload the NorthStar Sales By Members And Items report for the shop and the caddie master — the same report the Data tab and the member profile read. Checks here are never visits and never surveyed. Sales are the Sub Total — after discount — and refunds come off the day they were given. Uploading the same report twice changes nothing.

By location

Day by day

Net sales per trading day, shop and caddie apart. Days the shop did not trade are not drawn as zero.

By day of the week

Average per trading day, so a period with five Saturdays does not look like a good Saturday.

By membership category

Members only. House accounts and guests are in the takings above and not here.

Who rang it

Top members

One day’s checks

Racquets surveys

Court condition, booking and overall scores from surveys sent after a game.
Average score
--
Racquets NPS
--
Response rate
--
Responses
--
By sport
No responses yet
Average scores
No data yet
Recent responses · last 5
No responses yet

Upload court bookings

The booking export, as CSV or Excel. Cancellations are skipped, a member on two courts in a day is asked once, and a court booked for a day that has not happened yet is held back until it has.
🎾
Drop the booking export here, or click to browse
CSV or Excel (.xlsx) with Amenity, Time, Status and User columns
Processing...

Racquets survey log

Every game recorded, with the sport and court it was on. A booking that never became a survey is listed as Not eligible.
Loading...

Survey sent after a game

The questions members see after their game live in Survey Builder, with every other survey the club sends.
Loading…

The night

Covers, sales and what happened, block by block. Everything saves as you type — a phone that locks at eleven does not lose the block — and filing one is a separate press, so a service that genuinely did nothing files zeros and is still a different thing from one nobody has been asked for.
Total revenue
--
Food + beverage + takeout
Total covers
--
Dining covers only
Occupancy
--
Covers over seats
Blocks filed
--

Service blocks

Each block asks for what it actually has: the à la carte rooms take reservations and sell takeout, the pool counts check-ins, the Trap has a bartender and no servers. Which is which — and what each block seats, which is what occupancy is worked out against — is set in Settings → Service recap.
Loading…

History

Every night the club has filed. Spend per cover across a period is the period’s revenue over the period’s covers, never the average of the nightly figures — that would weight a Tuesday with four covers the same as a Saturday with three hundred.
Loading…

The day’s notes

Banquets, beverage, billing, facilities, the handover, dress code. These belong to the night rather than to any one service — on the paper sheet each one happens to line up with a block, which is only where it fitted on the page.

Raise one

An issue goes to somebody who can act on it, and they are emailed straight away. A recognition names the person it is about, and they are told. Both end up on one list below.

Open and recent

Loading…

For the leadership meeting

Who has been named favourably, one row per person rather than one per mention — twelve rows for the same server makes them look like the only person in the building and pushes everybody mentioned once off the bottom of the page.

Write one up

A name and a date start one. No event has to exist first — attach one later only if the occasion was also surveyed. Everything saves as you type; completing it is a separate press.

Occasions

Drafts are listed beside the completed ones and marked as drafts — an occasion somebody started and never finished is exactly what this list is for.
Loading…

The occasion

Against the BEO
--
Covers attended
--
Beverage cost
--
Beverage cost
Outstanding
--
Charges
The write-up

The season

Only completed occasions are in any figure here — a half-written Saturday is not a Saturday that happened. Occasions with no BEO recorded are in neither side of the BEO percentage.
Loading…

Survey templates

Each survey type uses its own question set. Members see the template attached when the survey is sent.

What the member receives

Exactly what goes out for this template — the same text the sender uses.

New survey template

Club profile

FieldValue
Club name
Time zone
Currency

Outlets

Building rolls several tills into one row on Overview and F&B — a clubhouse that rings up under three revenue centres is one room to the member who ate in it. It is a label, not a merge: the outlets stay separate underneath, so sending, thresholds, ownership and alert routing are unaffected and it can be undone by clearing the field. Leave it empty for an outlet that is its own building. The name, the minimum spend that qualifies for a survey, how many days before a member can be re-surveyed, and which questions they are asked. That window counts surveys that were sent; one that went unanswered for longer than the no-reply period set in Settings stops holding the member back, so somebody who never replied is asked again on their next visit rather than at the end of the month. Leave the questions on "Default for visit type" for ordinary dining; choose a template when an outlet needs its own, such as a racquets centre or a lesson. Who answers for the outlet is set below, under Case alert rules. Changes save automatically.

Add outlet

Case alert rules

Escalate anything unresolved after hours
Who hears about a poor response, and who picks it up if nobody does. Auto assign to and email owns the case — it is assigned to them the moment the alert is raised and emailed straight to them, and it is the same person who gets the outlet’s weekly training plan and its coaching actions. Email also to is copied on the same message without owning anything. If unresolved is who it goes to once the clock above runs out; the clock starts when the member replied, not when somebody next signs in. Leave any of them on "Nobody" and the managers are told instead. Changes save automatically.

Events

Events have no outlet, so they name their own people. Set the department line and you are done; give a kind of event its own names only where somebody else runs it.

Service recap — who it goes to

The night, as a PDF, to people with no account here — an owner, the board, the club president. Commas, semicolons or one per line; Name <addr> is fine and gets stripped down to the address. Sending is refused while any service is still unfiled, for the same reason sign-off is.
Loading…

Event recap — who it goes to

An occasion's write-up, as a PDF. Club management receive it when a recap is completed; the list below is for people outside the club — an owner, a board member — and that mail waits on you switching it on. A separate list from the nightly recap's. Sending is refused on a draft.
Loading…

Service recap

The blocks on the end-of-day sheet. Owner is who files one — a block with no owner is open to anyone who can reach the screen, because the alternative is a block nobody can file until somebody visits this page, and the day does not close. The F&B Director and above can file any of them. In use takes a block off tonight's sheet without touching anything it has already filed. The tick boxes decide what a block is asked for: a Men's Grille with takeout switched off is never asked for its takeout sales again. Seats is what the block holds, and what its occupancy is worked out against — blank for a block the club has not counted, which gives no occupancy figure rather than one of nought. Winter is what it seats once the pool and the Golf Patio close; zero for a room that shuts. Changes save automatically.
Loading…

Servers

Front-line servers and waitstaff credited with sales — this is the list the Server dropdown offers when you log a visit, and who receives a shift survey. Separate from Team members above: a General Manager does not belong here unless they actually work the floor. A phone number or email is what makes someone reachable — anyone without either is credited for their sales but cannot be sent a shift survey. Edit a phone or email directly in the list; changes save as you leave the field.
Add a server under Team members → Add a person, choosing Servers — one place for everyone, whichever list they belong on.

Survey delivery

Surveys are queued when shift data is uploaded and go out once a day at the time you choose here. Changing the time takes effect straight away — if the new time has already passed today, that day's batch goes out within a minute. Nothing is ever sent between 8 PM and 8 AM Eastern.
Eastern Time

Weekly analysis

When Training Actions and AI Insights are written. Reads the week's scores and comments for each outlet and produces one training plan per outlet. An outlet with no responses that week gets no plan rather than an empty one.
Eastern Time

How often one member can be surveyed

Off unless you turn it on: by default every qualifying visit is surveyed. Several cheques at the same outlet on the same day already count as one visit, so this only affects a member who used different outlets. Set a cap and the highest-spend visit is the one surveyed — the rest are dropped rather than saved for later, and show on the send log as skipped.

Asking again when nobody replied

Each outlet's Re-survey days stops a member being asked about the same room too often. It counts surveys that were sent, so a member who never opened one was unaskable for the rest of that window even if they were in every week. Once a survey has gone this long with no reply, it stops holding them back and they are surveyed again on their next qualifying visit — nothing is sent in the meantime. A member who did answer is left alone for the full window. Set this to Off to keep the old behaviour.
Member app Not set up
If your club runs its own member app, surveys can go through it instead of by text. Every member is pushed first and the app tells us, there and then, whether it reached their phone; anybody it could not reach is sent the usual text or email in the same run. Nobody misses a survey because of this, and every push that lands is a text you are not paying for. The app sends its own wording — there is nothing to write here.
Testing pushes nobody: it sends one request for a member number no club issues, so the only thing it proves is that your app accepted us. Safe to run before the switch above is ever turned on.

Staff survey occasions

Ask a named group about a named night. Give it a name and a date, upload the roster or pick who worked it, then schedule it or send it now. Answers come back anonymously: they are stored with no link to the person who wrote them, and held back entirely until enough have come in that no single one can be traced back.
Leave the send date empty and nothing goes until you press Send. A time scheduled late holds until the morning rather than texting somebody at one in the morning.

Team members

Staff who can be assigned case alerts and manage the system. Each role sees only what it needs. Adding someone here does not put them on the Servers list below — that is who gets credited with a cheque and sent a shift survey. Somebody who does both belongs on both.

Access for

View opens a screen and refuses every save on it. Edit does both. The server enforces this, so a screen set to None is an API that refuses them too — it is a permission, not a tidier menu. Starting point: the default.

Add a person

One place for everyone. Team members hold a role and sign in to this dashboard. Servers are credited with cheques, appear in the Server dropdown when you log a visit, and receive shift surveys. Somebody who does both goes on both lists.

Upload a roster

Same "Add to" choice as above. Paste from a spreadsheet, or choose a CSV. First row must be the column names. Team members needs name (or first_name and last_name) plus optional email and role. Servers needs name plus optional phone and email. Anyone already on the list is updated rather than added twice. This does not create dashboard logins — do that below, one person at a time.

User accounts

Create dashboard logins for team members. Only Super Admins and General Managers can manage accounts.
All
Common questions

Common questions

Each of these is answered by a screen. Work down the path and stop at the first thing that looks wrong.

Help articles

Step-by-step guidance for every screen. Select an article to read it.