An AI teammate is a named member of your workspace with a job, a voice and exactly the access you give it. It reads your tables every morning, tells you what needs a person, and puts every change it suggests in front of somebody before it counts.
The product itself. Maya's brief was written by the AI from the salon's real bookings. Not a mock-up.
A job is offered only where your workspace can run it, and its card says what it would find in your data right now. You choose its name, its colour and how it writes. Hiring never adds a table or a field.
Front Desk Manager
For a table that takes bookings.
Writes Warm, a short paragraph
Support Lead
For a tickets table with response targets, routing or an email address of its own.
Writes Plain, a sentence or two
Maya and Sam are the names each job suggests, drawn here as people to show who they are. In the app each one is a rounded square marked AI, where a person is a circle, so a teammate is never mistaken for a colleague.
Squares are AI. Circles are people. That holds in a cropped screenshot, and for anybody who can’t tell the colours apart.
Maya checks it within half a minute. Marco already has Mae Tran’s colour from 1:30 to 3:00.
NoticesJoss is free at 2:00 and already has two cuts today. One field changes, Staff, and only when a person says so.
Suggests a changeIt leads with the clash. Then the day: nine bookings, one with nobody on it, and a Sunday with no hours in the rota.
WritesApprove on the desk or in Approvals, and the change is made as Ellie. Decline it, and nothing changes.
A person decidesThe suggestion expires, honestly, rather than being approved too late. Nothing changes.
Expires
The tables its job needs, and any you tick. Every other table is closed to it, including the ones you add later.
Briefs and notes, on its own desk. Its sponsor is told when it writes, and anything it has nothing to say about, it leaves out.
A change to one field, which waits in Approvals. Any admin can decide it. It is made as the person who approved it.
A new teammate starts with a practice week. For its first 7 days its suggestions are marked Practice: you approve or decline them as usual, on your real data, and approving one changes nothing.
Once its suggestions look right, end the practice early from its desk. Or switch suggesting off when you hire it, and it only reports.
Approved in practice. Nothing was changed.
A seat price would suggest it replaces a person. It doesn’t, so teammates are included in every plan. Each one has a monthly limit of AI actions instead: a morning brief is one action, and so is each check a duty makes.
At its limit it pauses until the month turns, and tells the person it works for. It never goes over, and it doesn’t touch the AI allowance your team shares.
See pricingA brief every morning is about 30 actions a month. You choose the limit when you hire it, and an admin can change it on its desk.
How RowFold uses AI with your data: the privacy policy · security.
No. Teammates are included in every plan and never take a seat. Each one has a monthly limit of AI actions that you choose when you hire it: 100, 200 or 500. A morning brief is one action, and so is each check a duty makes. At the limit it pauses until the month turns and tells the person it works for. It never goes over, and its actions don't come out of the AI allowance your team shares.
It changes nothing itself and sends nothing: no email, no text, nothing outside your workspace. It writes what it finds on its own desk. Where a duty may suggest a change, the change waits until a person in your workspace approves it, and it is then made as that person. An applied change can be undone.
Only the tables its job needs and any you tick when you hire it. Every other table is closed to it, including tables you add later. It is hired as a viewer and is never an admin, so it can't change anybody's access, its own included. The person it works for must be able to see everything it sees.
Decline the suggestion and nothing changes. One nobody answers expires after 72 hours. If somebody edits the record first, the suggestion is withdrawn rather than written over the newer value. And for its first 7 days a new teammate is in a practice week: you answer its suggestions as usual, and approving one changes nothing.
Two today. A Front Desk Manager, for a table that takes bookings: it writes a morning brief, checks each new booking for a clash and can suggest somebody who is free, and speaks up about bookings with nobody on them. And a Support Lead, for a tickets table: it writes a morning brief about the queue, checks each new ticket for a duplicate, and can suggest an owner for tickets nobody has picked up. A job is offered only where your own tables can run it, and hiring never adds a table or a field.
No. A teammate's questions go to the same AI provider as the rest of RowFold's AI, in the same way, and your data is never used to train a model.
Pause on its desk stops every duty at once, and Resume starts them again. Let go removes it from the workspace for good. Its desk is kept, so what it wrote can still be read.
Neither. A teammate has no password and no way to sign in. Everywhere it appears it is drawn as a rounded square marked AI, where a person is a circle, and its name reads with its role, as in Maya · AI teammate.
Build or import your workspace, open AI teammates, and meet the job your tables can run. It writes its first brief before you close the page.
It's Shannon. And this is Maya. She runs the front desk at Cedarwood, a salon with three stylists. She's an AI teammate: a member of the workspace, with a name, a job, and somebody she works for. She can open the tables her job needs, and any you tick. Nothing else. She's never an admin, and every other table is closed to her.
Marco Linden is double-booked this afternoon — two overlapping appointments at 2:00 PM.
The double booking: Mae Tran · Color (1:30–3:00 PM) overlaps with Tom Becker · Cut (2:00–2:45 PM). Both are with Marco Linden, so one of these needs to move.
Bookings today and tomorrow: 9 today, 0 tomorrow.
Every morning at half past seven, she reads the day. And she writes it down the way a good colleague would. The thing that needs a person goes first. Marco Linden is double-booked this afternoon. Every booking she names is a link, and every number comes straight from that morning's bookings. When nothing needs anybody, she writes nothing at all.
Then a booking comes in. A two o'clock cut, with Marco. Maya checks it within thirty seconds. Marco's colouring Mae Tran's hair until three. So she suggests Joss, who's free at two and already has two cuts today. One field changes, from Marco to Joss. And only when somebody says yes.
Approved in practice. Nothing was changed.
A person always decides. Any admin can approve it, right on her desk. The change is made as whoever said yes, and it can be undone. If nobody answers in seventy-two hours, it expires. And her first week is practice: you answer her as usual, and approving changes nothing. You see what she'd do before she does any of it.
Maya keeps the front desk. Sam leads support, and watches the ticket queue. Neither one takes a seat, so they come with every plan. Each has a monthly limit, and pauses rather than going over. They see only what you give them, write what they find, and change nothing on their own. Hire one, and get its first brief before you leave the page.