[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Follow up Planity no-shows and block repeat offenders

> List the clients marked "Pas venu" in Planity each week and stop repeat no-shows from booking online, after your OK on each one.

Source: https://cotlet.dev/integrations/planity-api-mcp-server/follow-up-no-shows

Every Monday the owner opens the no-show tab, sees the same two names as last month and still has to open each client record to tick the box by hand.

Cotlet does it in your own Planity account with list\_no\_shows, get\_client and set\_client\_online\_booking, called by your AI agent, an n8n workflow or a script.

[Sign up free](https://cotlet.dev/app/signup?app=planity) [All Planity tools](https://cotlet.dev/integrations/planity-api-mcp-server.md)

Hosted · nothing to install or maintain

## Can Planity do this on its own?

Planity marks no-shows and blocks online booking per client, both by hand (checked 23 Oct 2026). It sends an SMS reminder 24 hours before each appointment and lets you ask for a prepayment at booking and set a cancellation policy. Nothing blocks a client after a number of no-shows, and no API reads them.

## How you do it in Planity today

1. A stylist or the owner marks a client who did not come as "Pas venu" in the agenda.
2. The owner opens the Admin tab, then "Statistiques RDV", then the tab "RDV pas venus", and picks day, week, month, year or a custom range.
3. The tab lists the appointments, not the clients behind them, so a client who missed twice is found by reading names.
4. For each client, the owner opens the Clients tab, searches the name, clicks the row and ticks "Empêcher ce client de prendre RDV en ligne" at the bottom of the window.
5. The owner saves with the green button at the top right. Nothing repeats this for the next week.

## How to follow up Planity no-shows and block repeat offenders

Prompt

```
List last week's no-shows in Planity. Block online booking for any client with two or more, and tell me who missed once.
```

1. 01  
### Read the week  
list\_no\_shows runs for the last 7 days and returns every appointment someone marked "Pas venu", oldest first, with no\_shows\_in\_period for each client. A no-show nobody marked in the agenda is not in the list, so the agent says how many it found rather than how many there were.
2. 02  
### Group by client  
The agent counts per client against the rule in your prompt, for example two or more in the window. A client above the line is a candidate. A client with one no-show only goes in the report, with the service and the staff member.
3. 03  
### Read the record first  
get\_client shows whether online booking is already blocked and which appointments the client still has. An already blocked client is skipped. A client with an upcoming appointment is listed for you with its date, because the block does not touch that booking.
4. 04  
### Block with your OK  
set\_client\_online\_booking with allowed false runs once per candidate. It decides whether a person can book, so each call waits for your OK until you switch confirmation off for this tool. Allowed true undoes it.
5. 05  
### Report  
The agent returns who was blocked, who missed once and who was skipped and why. It sends nobody a message: telling the client is yours to do.

### What you get back

Example data

```
No-shows 12 to 18 Oct: 3
Blocked from online booking: Léa Martin (2 no-shows: Coupe femme Tue, Brushing Sat)
Missed once: Noah Petit (Couleur, Inès)
Skipped: none already blocked
```

### Other ways to ask

- On the first of each month, list the no-shows of the past month per staff member and block no one.
- Block anyone with three no-shows in the last 90 days and list the rest with their dates.
- Let Léa Martin book online again.
- List this week's no-shows and draft a short message for each client, but send nothing.

## What Planity allows, and what to know first

- Only appointments marked "Pas venu" in the agenda appear under "RDV pas venus", so the list is as complete as the marking at the desk.
- The option "Empêcher ce client de prendre RDV en ligne" sits at the bottom of the client window and Planity describes it for clients who miss appointments.
- Planity sends an SMS reminder 24 hours before each appointment and offers partial or full prepayment at booking, so a block is a second line of defence.
- Every tab of Statistiques RDV can be shown by day, week, month, year or a custom range, which is the range list\_no\_shows takes.

set\_client\_online\_booking asks for your OK by default. To run it weekly without you, switch confirmation off for that tool in your dashboard.

Sources: [Planity Help: Where to find my appointment statistics](https://support.planity.com/hc/fr/articles/27962473121682-O%C3%B9-retrouver-les-statistiques-de-mes-rendez-vous) · [Planity Help: How to manage a client record](https://support.planity.com/hc/fr/articles/28163774235666-Comment-g%C3%A9rer-une-fiche-client) · [Planity Pro: Agenda](https://info.planity.com/solution/agenda-en-ligne)

## Call set\_client\_online\_booking from a script

curl

```
curl -X PUT https://cotlet.dev/api/v1/planity/clients/c_1042/online-booking \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"allowed":false}'
```

Example response

```
{
"client_id": "c_1042",
"name": "Léa Martin",
"online_booking_allowed": false
}
```

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is planity\_write → set\_client\_online\_booking. Example data.

[Schedule it in n8n, Make, Zapier or cron](https://cotlet.dev/integrations/planity-api-mcp-server.md#automations)

## Planity tools this automation uses

__Cotlet Planity tools used to follow up Planity no-shows and block repeat offenders__
| Tool | Parameters |
| ---------------------------- | ------------------------------- |
| list\_no\_shows | date\_from, date\_to, staff\_id |
| get\_client | client\_id |
| set\_client\_online\_booking | client\_id, allowed |

[All 14 Planity tools with descriptions](https://cotlet.dev/integrations/planity-api-mcp-server.md#tools)

## Frequently asked questions

### Is it safe to connect Planity to Cotlet?

Yes. You sign in to Planity yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Planity once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

## More Planity automations

- [Block staff time off in the Planity agenda](https://cotlet.dev/integrations/planity-api-mcp-server/block-staff-time-off.md)
- [Weekly Planity booking report](https://cotlet.dev/integrations/planity-api-mcp-server/weekly-booking-report.md)
- [Planity API and MCP server: every tool](https://cotlet.dev/integrations/planity-api-mcp-server.md)
- [All use cases](https://cotlet.dev/use-cases.md)

## Give your agent access to Planity.

Free 7-day trial with 2,000 credits, no card needed. Cotlet is independent and not affiliated with Planity.

[Sign up free](https://cotlet.dev/app/signup?app=planity)

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.