← All playbooks · Raw API

concierge-pages

# Concierge pages — point.me

Paid consult / booking **pages** under `/concierge/`. Redirects from `/cc-consult`, `/c/strategy-consult`, `/mileage-runs`, `/c/booking-service` already point here — edit the **destination** page, not the old slug.

## URL patterns

| Public path | CMS slug |
|-------------|----------|
| `/concierge/points-consult/` | `concierge/points-consult` |
| `/concierge/full-service-booking/` | `concierge/full-service-booking` |
| `/concierge/mileage-run/` | `concierge/mileage-run` |

Markdown: `https://www.point.me/concierge/points-consult.md`. `contentType: page`.

## Typical stack (points consult)

| Role | Types |
|------|--------|
| Hero | Consult offer + price framing |
| Steps | What to expect (goals → 1:1 → plan) |
| Proof | Case-study style modules (Marina / Sunil / Edward on the live page) |
| FAQ | **FAQs** |
| CTA | Booking / plan CTAs — match the live page, do not invent a HubSpot demo form |

Clone the matching concierge URL. Do not use `/partnerships/` as the template.

## Workflow

1. `cms-edit open /concierge/points-consult/` (or the matching slug)
2. Preserve pricing and “what’s included” unless the brief replaces them
3. `preview urls` on staging → `diff` → `save` → `task-publish-handoff`

## Out of scope

- AWS authenticated booking
- Partnerships Gateway demo forms