Help Center
Docs

Operator Workflows

How Laureo plans, prepares, asks, approves and hands off multi-step work

From intent to outcome

Clear requests proceed; what only you can answer is asked on a card.

1

Understand the goal

Laureo works out whether you want an answer, a change it can make, or a page you need to open.
2

Fill in what it can

It takes values from your words, the record on screen, your profile and the form's own defaults. Each value on the card says where it came from: From your message, From your profile, Default or Filled in for you.
3

Prepare within your authority

It reads and makes changes through the same plan, role and record-scope rules as the app. An action the chat does not do yet gets one line and an Open button for its page, and the rest of the request carries on.
4

Ask at a real boundary

A value only you can give comes as a question card. In Ask first, every change shows its card before it is saved.
5

Return the result and receipt

The receipt says what was saved, with Open on the record, Copy for its address where it has one, Undo where the change can be reversed, and the defaults it used.
Laureo never infers recipients, legal consent, destructive targets, security or permission changes, external publication, or financial commitment.

The question card

Asked only for what Laureo cannot work out.

When an answer only you can give would change the outcome, Laureo asks for it on one question card: up to four questions, each with its choices or a control of its own, such as days, hours, a date, a number or a record to pick. Where the value is free, a box lets you type your own answer. The card ends Laureo's turn, and your answer is your next message.

Each question has You decide, which hands that one back to Laureo, and an optional question also has Skip. Pressing Let the assistant decide without touching the card hands every question back. A question only you can answer, such as a decision in a move from another CRM, has no You decide: its button reads Send answer and waits until you pick.

It never asks for a value it can write, look up or take from a default. An email subject is written for you, and a quote takes your workspace's currency. A field the change card still needs from you sits at the top of that card, under Needs your input, and Approve waits until it has a value.

A question card never approves anything. In Ask first every change still shows its own card before it is written, with every value it will save.

Exact action approvals

The effect that runs must match the preview you approved.

An exact action approval is bound to the persisted run and conversation, exact targets and recipients, content version, risk, and a fingerprint of its parameters. Edit on the card invalidates the old approval, creates a new card with your values, and approves that new card in the same step. Request changes declines the card with your words, and Laureo shows a revised card in its place.

The decision saves immediately, but the web request does not own the effect. A background worker rechecks your current membership, seat, role, plan, grant, feature, record scope, record version, recipients, and approval fingerprint before it acts.

Batch previews identify whether a subset is allowed or all items must succeed together. Every item receives an explicit decision; editing one item creates a new preview for that item. Repeated clicks, tabs, retries, or worker restarts cannot claim the same effect twice.

Create a quote

One card, every value it will save, and one result.

For example, ask: "Prepare a quote for Acme Corp for the onboarding package." Laureo shows one card with every value the quote will be saved with, grouped as the quote form groups them. A value it filled in from a default, such as your workspace's currency, reads Default; a required field it could not fill sits under Needs your input, and Approve stays off until it is set.

Laureo does not invent a price or a financial commitment. After you approve, it creates exactly one quote, and the receipt carries an Open link to it. A product that is not in your catalogue yet can be added on the same card as the quote, under one approval.

Once the quote exists, an edit of it can set After payment, send them to book: the booking page whose private link the payer gets once the quote is paid, or None. The card names the page before and after. You need access to booking pages for this field, as on the quote page, and an invoice edit can set the same field.

Booking pages and campaigns

Booking pages, campaign drafts and their sends, each on its own card.

Ask for a booking page with its days and hours, for example Tuesdays and Wednesdays from 8 to 10 and from 2 to 5, and Laureo shows one card: the page's real address, its days and hours in your time zone, the length, the place and who can book, with the editor's other settings under More settings. In Ask first, nothing is created until you approve, and the result gives you the live link.

Laureo can also change a booking page, turn it on or off, and delete it. A delete always shows a card where you type delete first. A page with bookings to come offers Turn off instead, or a second card that names how many bookings the delete cancels. A price is a step of its own, after the page exists, with its own card every time, and it needs the permission to charge payments.

"Draft a campaign to my customers" creates a campaign draft, shown on a card first. A draft needs no sender: Laureo does not ask you for one. The sender is checked when you send a test, schedule the campaign or send it. Once the draft is saved, its card offers Edit campaign, which opens that campaign, with its audience, in the campaign editor.

Campaign drafting reaches nobody. Scheduling and sending reach recipients, so each shows its own card every time, in every mode.

Next steps after a change

One Open, up to two next steps, and nothing runs by itself.

After Laureo creates or updates a record, a row under the answer offers Open for that record and up to two next steps for it. Open shows the record in place, with a way to its full page. A step is a prompt: pressing it sends it as your next message, and nothing runs until you press it.

Reach, and the steps that stay yours

A few actions are still done on their own page, and some steps are always yours.

Laureo runs an action only when it can run it with exactly your access, through the page's own rules. A few actions in the app are still done on their own page. For those, Laureo says so in one line with an Open button for that page, as an extra, and carries on with the rest of your request. What Laureo Can Do lists what it does in the chat today.

Some steps are always yours: connecting an outside account, paying or entering a card on the secure payment page, giving consent, completing a two-step sign-in, typing a confirmation word, and entering a secret such as a key or a password. They happen inside the card, through the page's own control, and Laureo learns only whether each one was done. Deciding an approval stays yours too: an answer that lists one waiting for you carries your own Approve and Deny buttons.

Laureo never moves the screen on its own, and it never pretends an action was done when it was handed to you.