Payment reminders that report whether they landed, renewals and notices on schedule, onboarding that runs itself, campaigns on live data, and webhooks into whatever else you run.
Half the recurring work in a flex space is somebody's memory: chase the invoice, flag the renewal, send the welcome email, update the sheet. When that person is on leave, the work does not happen, and you find out through the bank balance.
Before due, on due and after due, on email and WhatsApp, with the result of each attempt recorded per channel. A message that failed to deliver shows up as a failure rather than as a customer who did not pay.Chasing that never silently stops
Terms approaching expiry, notices given, agreements coming up for escalation and seats about to release are surfaced as work with a date on it, and the routine parts happen without anyone starting them.Nothing expires by surprise
A new member gets the welcome message, house rules, wifi, app login and door credential in the order and on the channels you configured, per centre. Every member gets the same start regardless of who is on shift.Consistent onboarding, zero effort
Build an email or WhatsApp campaign with real merge fields from member data, honour unsubscribes and one-click list headers, and see who opened and who replied. Marketing stops living in a separate tool with stale lists.Lists that are never out of date
Build rules over your own events: a lead goes cold, an invoice is a week late, a service request breaches its due time, occupancy at a centre drops below a threshold. Each fires a notification, a task or a webhook.Exceptions find you, not the reverse
Push events out to n8n, Zapier or your own service, and pull leads in from aggregators and your website. For teams that want more, we deploy and run a private automation stack per client.Fits the stack you have
Automations record the actual channel result, and a job that stops running raises an internal alert rather than failing quietly for a month.
Every automation can be paused, previewed and tested on one record before you point it at the whole customer base.
Each automated message and action is on the customer timeline, so your team can see what the system already said before they call.
A workflow tool bolted onto five disconnected systems automates the copying between them. Here the trigger is the business event itself.
Reminders fire off real invoice state, and stop the moment the payment is actually recorded.
Renewals, notices, escalations and expiries come from the agreement, not from a calendar entry.
Ageing deals, missed follow ups and quiet prospects surface as work with an owner attached.
A request past its due time escalates to the right person instead of waiting for a complaint.
Automations are deterministic. You define the trigger and the action and it runs exactly that way every time, which is what you want for invoices and renewals. Agents handle conversation and judgement. Most operators use both, with automation on money and lifecycle and agents on sales and support.
Yes. Channels are chosen per automation, and the result of each channel is recorded separately so you can see which one actually reached the customer.
Scheduled jobs are monitored, and one that has not run when it should raises an internal alert. Delivery results are stored per attempt, so a failed send is visible on the record rather than assumed to have worked.
Yes. Webhooks carry events like a new lead, a signed agreement or a paid invoice into n8n, Zapier or your own endpoint, and leads can be pushed in from your website or an aggregator.
No for the standard automations, which are configuration. If you want a bespoke workflow across several systems, we run that as a service and build it for you.
Bring one floor and last month of invoices. We will set it up live and you can decide from there.