Automation Suite
Her week was the same tasks, again and again.
Sofia Lindqvist runs a small training and services company.
The desk at the end of the day.
Every task on it repeats tomorrow.
The flagship, at work
Watch it work out the dates.
The Appointment Reminder video.
Filmed on the checked test run. It will go here when it is recorded.
Two reminders. Zero remembering.
- The week. Sofia's desk at night: forms, sticky notes, a full tray. The same work of a small company, all done by hand.
- The booking. A dental check-up and cleaning at Northgate Dental Studio, 14 November at 11:30 am. The Appointment Reminder does the rest.
- The plan. Reminder one: 13 November, 11:30 am, exactly 24 hours before. Reminder two: 14 November, 9:30 am, exactly 2 hours before. The tool plans and writes them. In the demo, nothing is sent.
- The message and the record. The message writes itself. It has the patient's name, the service, and the time. One line helps keep the slot: reply YES to confirm, or call us to reschedule. The booking is saved with both reminder times.
The Appointment Reminder video.
Filmed on the checked test run. It will go here when it is recorded.
- The certificates. A class list goes in. Three certificates come out. Each has a name and its own ID. The list of who got one matches the files.
- The follow-up. A new lead from 9 November gets a welcome at once. Then a follow-up on 11 November and a check-in on 16 November. All planned, written, and saved.
- The result. Nine workflows, each tested with a real run and a saved record. The desk is clear. The machine repeats. The human decides.
Chapter two · Certificate Generator
A class list in. Certificates out.
One list goes in. One certificate comes out for each person. It has the name, course, date, and its own ID. It is saved as a file, with a list to match.
Certificate of Completion
Ayesha Rahman
Prompt Engineering for Trainers
PEFT-2026-001
- Ayesha Rahman. PEFT-2026-001.
- Tanvir Hasan. PEFT-2026-002.
- Maria Gomez. PEFT-2026-003.
Three certificates from the checked test run. Made as files, checked, and the list matches. 9 November 2026.
Chapter three · Lead Follow-up
The follow-up plans itself.
A lead comes in once. The tool writes the welcome, the follow-up, and the check-in. Each has a date. Each is a draft for a person to approve. The lead is saved in one row.
- Day 0The welcome9 November 2026, written at once
- Day 2The follow-up11 November 2026, dated exactly
- Day 7The check-in16 November 2026, dated exactly
Dates from the checked test run. A lead from 9 November gave day 2 and day 7 just as planned, with drafts made for the person, and one full saved row. Written, not sent.
The suite, counted
9
Nine workflows. Each one was tested from start to end with a real run. The runs worked. The results were checked. Nothing was made up. Six more ideas wait behind them. They are marked as ideas wherever they show.
The problem
Routine work eats skilled hours.
Questions come in all day. A person reads each one and writes a reply. One inbox mixes complaints, bills, and forms. All of it waits for one person. The work is not hard. It never ends. And it is done by the best-paid people in the room.
Meetings are soon forgotten.
A meeting ends. Choices are made. Promises are given. By next week, no one can prove them. Notes depend on who wrote them. Next steps depend on who remembers. The same points come back, because nothing was saved where people can find it.
Follow-ups depend on memory.
A new lead gets a warm first reply. Then silence. Day two and day seven happen only if someone remembers. Most leads are not lost to a better rival. They go cold in a busy week. No one sees it until the month ends.
Paperwork done by hand leads to errors.
Certificates typed one by one come back with wrong names. Feedback forms pile up unread. By the time you read them, it is too late to learn from them. CVs are checked one way on Monday and another way on Friday. Hand work drifts. No one sees it until a client or a job seeker pays for it.
How it works
Nine workflows. One rule.
A person approves before anything goes to another person. The suite, grouped by who it helps:
- ClinicsAppointment ReminderBookings reminded twice, to the hour
- TrainersCertificate GeneratorA class list in, named certificates out
- TrainersFeedback to SummaryForms in, one honest page out
- TrainersMeeting to ActionMeeting words in, clear next steps out
- BusinessesSmart Enquiry HandlerQuestions sorted, replies written as drafts
- BusinessesInbox TriageOne inbox, sorted and passed on
- BusinessesFair CV ScreeningScores a person can check
- BusinessesWeekly Content PipelineOne short plan in, a week of drafts out
- BusinessesLead Follow-upDay 0, day 2, day 7, planned
The project page also has a trainer kit and a clinic note tool. Change what goes in, and every next step follows it.
From demo to your business
The planning. What you saw is the real plan, tested from start to end. Dates worked out to the hour. Messages written. Records saved. Results checked by hand against what went in.
The sending. In the demos, nothing is sent. For real use, two steps are added under your own account. One waits until the right time. One sends on your own channel.
The approval. Drafts are made for you. Choices stay with people. Each workflow is built so a person approves before anything goes to another person.
The machine repeats. The person decides.
Give the week back to the people.
Set it up once with your bookings, class lists, and inbox. Then the suite repeats the work. Your team approves it.
Sofia Lindqvist and Northgate Dental Studio are made up. The booking, class list, and lead you see are demo data from the checked test runs of 9 November 2026.
The workflows you see run offline as a demo: reminders are planned and messages are written, and nothing is sent. For real use, a wait step and a sending step under the client's own account make them live.