Optional professional services — what to ask for
If you are adopting Member Access OS, you can run much of the configuration with your own staff. Many brands also buy extra help—for passes, training, door hardware, integrations, rollout planning, or tailored journeys that match recurring, credit-based, and hybrid billing. This page explains common types of assistance so you can compare proposals fairly and know what questions to ask.
What is included always depends on what you agree with your implementation partner; nothing below is implied by the software alone.
Passes and digital wallets
| If you need… | What that often includes |
|---|
| Pass design and rollout | Designing how member passes look and behave in Apple Wallet and Google Wallet—layout, imagery, how renewal and expiry appear, and consistency with how staff approve members. |
| Phone tap at the door | If members will tap a phone to enter, aligning pass fields, testing, and verification so on-site behavior matches what your marketing describes. |
Your site and the member journey
| If you need… | What that often includes |
|---|
| Member-facing pages | Signup, dashboard, and branding that feel continuous with your marketing, within the layouts your deployment supports. |
| Custom marketing / landing sites | External sites that pull branding and page blocks via the Headless landing API, plus interest-form POST and handoff to join. |
| Clear end-to-end journeys | Reducing confusion from join → payment or proof upload → approval → active membership: consistent wording across email, QR materials, and front-desk scripts. |
| Design matched to your model | When recurring memberships, prepaid credits, hybrids, or top-ups sit side by side—tailoring language, dashboards, and pass behavior so Join → Pay → Visit reflects how you actually bill, not generic placeholder copy. |
Your team’s day-to-day work
| If you need… | What that often includes |
|---|
| Training for staff and managers | How to handle Approvals, packages, and “stuck member” situations, and when to contact your rollout team or platform support. |
| Operational playbooks | Who approves when, how to cover peak times, escalation paths—beyond learning which buttons to press. |
Rollout planning and systems
| If you need… | What that often includes |
|---|
| Phased go-live | Piloting at one site before others, clear checkpoints, and a plan if you need to pause unattended entry at a location. |
| Integrations and reporting | Handoffs to finance or CRM tools your organization already uses, exports, and careful handling of member data—your organization remains responsible for lawful use and any legal review. |
Physical installation and on-site work
If you are adding readers, relays, or unattended entry alongside the software, installs often involve physical work as well as configuration.
| If you need… | What that often includes |
|---|
| Planning before install day | Where readers mount, cabling expectations, naming and labeling that match what you manage in Admin (fleet naming conventions). Prerequisites such as reliable power and network—before trades leave site—surfaced in §0 of the deployment checklist when door hardware applies. |
| Commissioning on site | Bringing gate software online, tying each physical reader to the correct record in your portal, HTTPS checks, and test entries (allowed and denied). Experienced teams usually prepare hardware in the workshop first so the visit stays within a short, predictable window—see on-site timing expectations; long first-time software installs should not happen while you are racing the clock at the venue. |
| Structured physical work (often a separate contract or your own contractors) | Strikes, mag-locks, electricians, locksmiths, or cabling. Your implementation partner may coordinate schedules and checklists; your venue remains responsible for building rules, fire regulations, and egress unless you have engaged licensed professionals for that separately. |
| Support on install day | A technical contact while trades finish work: re-run tests, record serials and labels, and confirm you are ready before you open the member path. |
After you go live
| If you need… | What that often includes |
|---|
| Keeping passes current | Updating passes when Apple or Google change requirements so members are not surprised at the door. |
| Ongoing support | Scheduled Q&A after go-live handover, or faster response options if your agreement includes them. |
Other supporting options
Add-on work that often complements the areas above—either in one project or in a later phase.
- Governance sessions — Decide together how much you trust automatic activation versus manual approvals, and write that down so desk practice matches your risk comfort.
- Moving members from an old system — Cleaning data, mapping fields, phased imports, and checks before you cut over—not only dropping a spreadsheet into a tool.
- Email that actually arrives — Choosing domains for member email, and coordinating with your IT on standards that help delivery; configuring the product is one part; inbox placement is shared with your organization.
- Clearer language and accessibility — Tightening readability on join and payment flows; a full formal accessibility audit is a different engagement if you need it.
- Business reviews — Periodic look at uptake, where members get stuck at approval, and alignment on what to improve next.
How to use this with your rollout
- Capture your organizational decisions early—the decision guide walks through them, including how long rollouts often take.
- Before you sign off go-live, use the handover checklist so you know what you should receive—written materials, access, and who to call—before your team runs day-to-day operations alone.
- If you are unsure which guides match your role, start with reading paths by role—then return here to compare service options.