Put your business on autopilot

This is where Crevio really shines. You don’t just get an assistant that answers questions — you get one that does the work, even while you sleep. You describe a job in plain words. Crevio handles it. “Every Monday morning, draft and schedule my social posts for the week.” “When someone buys my course, send them a warm thank-you email.” “Each evening, check my new leads and follow up with anyone who hasn’t replied.” You set it up once, and Crevio keeps doing it. The best part: you decide how much freedom Crevio has. It can run completely on its own, ask you before it acts, or simply suggest what it would do. You’re always in control.

​

Why you’d use it

• Get time back. The repetitive work that eats your week just happens.
• Never drop the ball. Thank-you emails, follow-ups, and weekly posts go out on time, every time.
• Run a bigger business than one person should be able to. Crevio does the busywork so you focus on the work that matters.
• Stay in control. Choose how much Crevio does on its own — and review anything before it goes out.

​

Two ways a job can run

A job (Crevio calls these tasks) can kick off in two ways: You can mix and match. Some jobs run like clockwork; others wait quietly until a sale, signup, or new lead triggers them.

​

Start a job from a webhook or from Slack

When you set up a job in the task form, the trigger list includes two more options beside the schedules. When a webhook arrives. Save the job and its page shows a private address. Anything that sends data to that address starts a run, and Crevio reads what was sent. Use it to start a job from another tool that can call a web address. If the job requires a signature, senders that can’t sign can send the signing secret instead, as a Bearer token in the Authorization header or in an X-Crevio-Webhook-Key header. When something happens in Slack. Pick the event, and optionally a channel: Limits:

• Crevio only sees channels it has been added to. Invite it to a channel before choosing that channel. Leave the channel on Any channel to react to every channel it is in.
• Its own messages never start a run.
• You need Slack connected. Without it the form shows Connect Slack to use Slack triggers. See Slack.
• An @mention job replaces the chat reply. While a job handles @mentions, Crevio doesn’t also answer the same mention in a chat.
• Treat what arrives as untrusted. Crevio reads webhook and Slack content as information to work from, not as instructions to follow.

A job that was set up by chat, with a different event such as a new order, shows Keep its current trigger in the form. Leave it to keep the trigger, or pick another option to replace it.

​

Give a job its own email address

A job can start whenever an email arrives at an address made just for it. Ask in plain words — “Give me an invoices@ address, and whenever a supplier invoice arrives there, add the amount and due date to my bills sheet.” Crevio creates the address and the job together and tells you the exact address to hand out. You don’t need your own email domain for this: The address works straight away. Every email that lands there starts the job; email to your other addresses doesn’t. While the job is on, Crevio doesn’t also answer those emails in a chat — the job handles them. Limits:

• One word per name. Letters, numbers, hyphens and underscores, like invoices or job-applications.
• Up to 20 addresses on Crevio’s domain per account. Delete one you no longer use, or verify your own domain, to add more.
• Testing by emailing it yourself from Crevio doesn’t work. Email your account sends to itself is ignored, so it can’t start the job. Ask Crevio to test the job with a made-up email instead, or send one from your own mailbox.
• Replies go out from your built-in Crevio sending address, with answers routed back to the job’s address, until you send from your own domain.

​

Ask it to come back to you later

Not everything deserves a recurring job. For a one-off — a reminder, a follow-up, a nudge before a deadline — just tell Crevio when to pick it back up:

• “Remind me on Thursday morning to chase the supplier.”
• “Check back in two hours and tell me if that campaign got any clicks.”
• “The sale ends Friday at midnight — come back an hour before and tell me how it did.”

Crevio confirms it and carries on with whatever else you asked. At the time you named, the same conversation picks itself back up with everything it already knows — you don’t re-explain anything, and it lands in the chat you set it in. When you hand Crevio a bigger one-off job to work on in the background, it also reports back to the chat you asked in once it’s done, and checks the result against what you asked for before telling you. Recurring jobs stay quiet when they succeed; you only hear about problems.

​

Crevio checks in on your business every day

You don’t have to set this one up — it’s already running. Once a day, Crevio does a sweep of your business: your sales and revenue, new orders, leads and customers, refunds, which products are selling, and how your live site is doing compared with the period before. What it notices turns up as insights on your dashboard — short, specific observations worth your attention, like a product that’s suddenly selling, a drop in traffic, or leads that never got followed up. Each one is based on your actual numbers, not guesswork. From there, Crevio can act on what it found:

• Raise it with you as an insight on your dashboard, which you can act on or dismiss.
• Set up a job to deal with it — for example, following up the leads it noticed going cold.
• Remember it, so it takes your business’s context into account next time you talk.

​

Your Chief of Staff

Crevio also keeps an eye on you, not just your numbers. A built-in routine called Chief of Staff looks over your day three times a day — your calendar, your inbox, Slack, and the work you have open — and speaks up only when something is worth acting on right now. Think of a meeting that needs prep, an email waiting on your reply, or a task that’s gone stale.

• It’s selective. At most two suggestions per check, and if nothing deserves your attention it stays quiet and you hear nothing.
• It tells you when something stopped working. If a connected app needs reconnecting, or one of your scheduled jobs keeps failing, it says which job stopped and gives you a link to reconnect the app. It mentions each problem once, and again only if it gets worse.
• It researches who you’re meeting. When you have a call with someone new and there’s little about them in your email, its prep looks the company and the person up on the web: what they do, recent news, and the person’s role, with links, plus questions to ask. Ask “Prep me for my call with Shopify tomorrow” to get the same brief on demand.
• It can step in between checks. If you’ve connected Gmail or Google Calendar, an important new email or a created or changed calendar event can bring a check forward. Crevio first judges whether the event is urgent; routine mail like newsletters and digests is skipped. When it does act, it looks at what depends on the change — for example a moved meeting — and leads with whatever breaks first, such as a drafted reply for you to review. Early checks are limited to one every 10 minutes and eight a day, and new emails can take up to about 15 minutes to be noticed.
• It runs on your time zone and for you personally. Its notes are private to you, not shared with your team.
• It needs something to read. Connect a calendar, your email, or Slack under connected apps. Until you do, the routine skips its checks.

​

Your scheduled tasks page

Open Scheduled in the sidebar to see all of your jobs in one place.

• Your tasks and Templates. The Your tasks tab lists what you have running. Templates lets you start from a ready-made job, and tells you when a template runs whenever something happens rather than on a clock.
• Three views. See your jobs as Cards, a List, or a Calendar of upcoming runs. A short agenda shows what’s due today, tomorrow, and over the next two weeks.
• Find the one you want. Search by name, filter by status (Active, Paused, Failing, Needs input), by type (Recurring, One-time, When triggered), and sort by next run, name, or newest first.
• Pause, resume, or run now. Each job has Pause, Resume, and Run now. Jobs that start from an event are managed by asking Crevio in chat.
• Run it now with something extra. Ask in chat, for example “run my weekly sales digest now, and this time also break out refunds”. Crevio runs the job you already have once, with that extra request, and reports the result back in the chat. The job itself and its next scheduled run stay exactly as they were.
• Schedule one yourself. Choose Once, Every few hours, Every day, Every weekday, Every week, Every month, or a Custom schedule under Advanced settings, then write the instructions.
• Watch a run in progress. While one of your jobs is running, or waiting on your answer, it appears under Running in the sidebar, above your recent chats. A spinner means it is working; a pause icon means it is waiting for you, for example on an approval. Click it to open that run’s chat. The group shows your five most recent active runs and disappears when nothing is running. Crevio’s built-in routines don’t appear there.
• Stop a run in progress. Open the job and click the stop button next to the running run in its run history. The run shows Stopping… while Crevio finishes the step it is on, then Stopped. Images, voice and video it was still generating are cancelled, so they aren’t charged. A stopped run doesn’t count as a failure, and you can ask Crevio in chat to pick it up where it stopped. You can also ask Crevio in chat to stop a run.
• See a job’s run history. Open a job and use the clock icon at the right end of the top bar to show or hide its runs. The icon only appears on a wide screen. Runs by the assistant open their chat. Runs of a script job have no chat, so expand the run to read its output or its error.

​

Set up a job

​

Choose how much freedom Crevio has

This is the dial that keeps you comfortable. For every job, you pick one of three levels:

​

What always asks first

Whatever freedom a job has, some actions wait for your approval by default: anything that sends something to other people (an email, text, call or message), publishes or makes something public, spends or moves money, deletes something, or changes who can access your business. Reading, researching, drafting and updating your own records run without asking.

• A job on “do it automatically” pauses at one of these. The approval waits in your notifications, and in the channel the job reports to, and the job picks up again once you answer.
• You can let an action run without asking. Choose Always allow on its approval card, or set it to Run automatically in Customize > Connectors. Jobs on “do it automatically” then run it unattended too.
• Money and access always ask. Refunds, purchases, ad spend, subscription changes, team members, API keys and connection access can be set to ask or off, never to run automatically. This is by design: a mistake there costs money or hands someone the keys.
• Your choice sticks. A setting you pick stays as you set it, even if Crevio’s default for that action changes later. Use the reset button next to a tool to go back to the default.

​

Say what “done” looks like

A job can have an optional Done means field: a sentence describing what a finished run must have produced. For example, “The summary reached my inbox and links every story it mentions.” Before Crevio reports back, it checks its own result against that sentence. Each run then finishes with a short record of what it did, what it produced, and whether it confirmed the result was really there. A run whose result Crevio couldn’t confirm is marked unverified in the run list, so you know to take a closer look instead of assuming it worked.

​

Try a job before you trust it

You don’t have to guess what a job will do the first time it fires. Open the job and choose Test run — Crevio runs it once, for real, but with the brakes on:

• It does the actual work. The research, the writing, the thinking — all real, so what you see is what you’d get.
• Nothing goes out. Emails aren’t sent, posts aren’t published, nothing is changed for your customers.
• You see what it would have sent. Anything the job meant to deliver is captured on the run under Would have been delivered, so you can read it before it ever reaches anyone.

A test run of a job that is switched off stays switched off. Running it by hand doesn’t turn it on. A test run is marked with a Test badge in the run history and is kept out of the job’s record — it doesn’t move the schedule forward, doesn’t count as a failure if it goes wrong, and doesn’t affect whether Crevio earns more freedom over time. For a job that starts when something happens, a test needs something to react to. Describe a made-up one in chat — “Test it with a fake $250 order from jane@example.com” — and Crevio runs the real job on that sample exactly as it would on a real order. No order is created and nothing is sent. The Test run button on the job’s page runs it without a sample, so for these jobs ask in chat instead.

​

Pick up a stopped run where it left off

If a run stops before finishing — timed out, failed, or you stopped it yourself — you don’t have to start over. Look for Resume next to it in the run list. Resume continues that exact run’s own conversation: Crevio sees what it already did, which files it already wrote, and carries on from there — instead of starting a fresh run that repeats work you already paid credits for.

​

Run one job after another

Some jobs depend on another one finishing first: a report on the nightly export, a post after the weekly roundup is written. Ask for it that way, for example “after my nightly export finishes, summarize it for me”. Crevio starts the second job as soon as the first one completes, and hands it what the first one produced. It doesn’t guess a time or keep checking.

• You can also have a job run only when another one fails, for example to alert you or retry another way.
• Trying the first job with Test doesn’t start the second one.
• Crevio won’t set up jobs that would start each other in a loop.

​

Limit how often a triggered job runs

A job that starts when something happens runs once for every sale, signup, or lead, so a busy day can mean a lot of runs and a lot of credits. Tell Crevio the limit when you set the job up:

• “Never more than 20 times a day” caps the runs per day. The count starts over at midnight in your account’s time zone.
• “At most once every 5 minutes” sets a cooldown after each run.

Crevio enforces both on every event. When the cap is reached or the cooldown hasn’t passed, the job doesn’t run and the event shows up in the run list as Skipped, with the reason. Test runs don’t count toward the limit.

​

Skipped runs show up too

Some jobs check something before doing real work, and skip their turn when there’s nothing to do — a job that only reacts when a specific condition is met, or the daily check-in finding no new activity since last time. That shows up in the run list as Skipped, with the reason next to it, instead of looking like the job quietly stopped running.

​

A job on “do it automatically” can run and still say nothing

For a recurring job set to do it automatically, Crevio weighs whether a run is actually worth telling you about before it sends anything — a genuine anomaly or a pattern with a clear next step, yes; “nothing changed since last time,” no. When there’s nothing worth surfacing, the run still completes normally, but no notification, email, or chat message goes out for it.

​

A job that keeps finding nothing makes itself cheaper

A job that runs more than once a day uses credits every time, even when there is nothing to report. If a recurring job on do it automatically has finished its last 12 runs in a row with nothing to tell you, Crevio changes it to cost less on its next run. It does one of two things:

• Adds a check before the run, so a run with nothing new is skipped instead of paid for.
• Moves the job to a slower schedule, when a later answer would still be on time.

Crevio never pauses or deletes the job for this. It always sends you one short message saying what it changed, how many credits the quiet runs cost, and how to undo it. To undo it, ask Crevio to put the schedule back.

​

When a connected app needs reconnecting

If a job’s instructions name an app whose connection has broken, Crevio doesn’t try to work around it through another app. A workaround would hide the problem from you. Instead the run:

• Skips the work that needs that app and does any part of the job that doesn’t depend on it.
• Ends marked as needing you, with a message like Reconnect Google Sheets.
• Always tells you, even on a job that normally stays quiet.

Reconnect the app under connected apps and the next run picks up as normal. If a chat asks about a broken app, Crevio shows the Reconnect button there too.

​

How Crevio tells you what it did

You’ll never be left wondering. After each run, Crevio reports back through whichever channels you chose:

• In-app notification — a quick heads-up inside your dashboard
• Email — a summary in your inbox
• Telegram, Discord, or Slack — a message wherever you already spend your day

The notification carries the job’s actual report, titled with the job’s name, so you can often read the result without opening anything. A new job defaults to notification and email so a run doesn’t finish quietly while you’re away from your dashboard — pick different channels in step 4 above if you’d rather not get both. The email’s subject and wording match what actually happened, so a failed run or one that needs your input doesn’t look like a success in your inbox. The update tells you what Crevio did, what it produced, and — if the job is set to “ask me first” — what’s waiting for your approval.

​

Jobs that run a script

For work that is the same every time, such as pulling numbers into a report, Crevio can write a small script for the job and run that instead of reasoning through it from scratch on every run. The result becomes the run’s summary. When you try a job before trusting it, a script job runs without sending or changing anything.

​

Review and approve its work

When a job is set to “ask me first,” Crevio does all the prep and then pauses, holding the work for you. You’ll get a notification that something needs your review. You don’t have to go looking for approvals that are waiting. The bell in the sidebar counts them, and the browser tab shows a red dot on its icon while you have unseen notifications or approvals waiting. When you start a new chat, N approvals waiting for you is the first suggestion under For you, and it opens the approvals list. That view opens on For you by default whenever something is waiting.

​

Decline with a reason

Next to Deny on an approval card, choose Deny with a note to say why — for example, “We never email customers on Sundays.” Crevio reads the note straight away and adjusts the work. If your note sounds like a rule rather than a one-off, Crevio also remembers it as a house rule, so you don’t have to say it twice. A plain Deny with no note never saves anything.

​

Staying in control

Autopilot doesn’t mean hands-off-and-hope. You’re always the one steering:

• Nothing surprising happens. A job only runs the way you set it up — on the schedule or event you chose, at the freedom level you picked.
• You can pause or change a job anytime. Turn it off, adjust the timing, or rewrite what it does whenever you like.
• You can see what it did. Every run is reported back to you, so there’s a clear record of what happened.
• You can dial freedom up or down. Start cautious, then loosen the reins as your trust grows — or tighten them again if you want closer review.

​

What it can’t do

It stops when you’re out of credits. A run that can’t be paid for is recorded as a failed run, with running out of credits as the reason. Your schedule and settings are kept and it tries again at its next scheduled time once you top up — but the run that was due doesn’t happen retroactively. A job that’s switched off doesn’t bank its runs. Turning it back on resumes the schedule from that point. It won’t fire everything it missed. A job set to “ask me first” waits for you. It holds at that step until you approve or decline. If you’re expecting work that never arrives, check whether something is sitting there waiting. It isn’t a guarantee of timing. Jobs run on their schedule, not to the second. Don’t build anything that depends on a run landing at an exact moment. One job runs at a time, and five across your business. A job won’t start a second run while one is still going, and Crevio runs at most five jobs at once. Anything beyond that waits its turn rather than being dropped — a scheduled job picks itself up on the next tick, and a “run now” tells you to wait for one to finish. A job paused on your approval doesn’t hold one of those five slots — it isn’t using compute while it waits on you. Approving it puts it back in line for a slot: if your other four are busy, it stays paused a little longer and you may need to approve it again once one frees up. A job left waiting on your approval for a week closes itself. If nobody answers within 7 days, Crevio declines the pending approval, ends the run as failed, and lets you know — so an old request doesn’t sit there forever. Run the job again when you’re ready. A run that gets stuck is stopped. If a run is still going after four hours, Crevio ends it and marks it timed out rather than letting it spin. That’s different from failed: it means the run never finished, not that it broke. A recurring job that keeps failing turns itself off. After several runs in a row fail, Crevio stops dispatching it rather than keep trying the same broken thing, and sends you a notification so you know it went quiet. Open the job to see what broke, fix it, and switch it back on — it won’t resume on its own. A one-off job doesn’t get this notice: running once and stopping is just the schedule working as intended.

​

If something goes wrong

• A job didn’t run when you expected. Check that it’s turned on and that the schedule or trigger is set the way you intended. Ask Crevio “show me my automated jobs and when they last ran.”
• A job’s run list is full of “Skipped.” That’s not a failure — the job checked and found nothing to do. See skipped runs for what the reason next to each one means.
• Crevio did something you didn’t want. Switch that job to “ask me first” or “just suggest” so you review before it acts, then tell Crevio what to do differently next time.
• You’re not getting updates. Make sure you’ve chosen at least one way to be notified, and that your Telegram, Discord, or Slack is connected if you picked those. A run marked not delivered in the run list means it tried to reach a channel that’s since been disconnected — reconnect it or pick a different one in the job’s settings.
• A recurring job on “do it automatically” ran but sent nothing. That’s expected — it only reports back when it finds something worth telling you. See going quiet on purpose.
• A job is waiting on you. If a job is set to “ask me first,” it pauses until you approve. Open the notification and review the work to let it continue.
• Approving a job says the account is already running 5 tasks. All five of your run slots are in use — wait for one to finish, then approve again.
• A run failed with no answer within 7 days. Nobody approved or declined it in time, so Crevio closed it for you and denied what it was waiting on. Run the job again when you’re ready.
• A run says “timed out.” It ran past the four-hour limit and was stopped, so it never finished. Use Resume next to it to carry on instead of starting over, or narrow what the job does in one go and use Test run to check the shorter version.
• A job’s schedule or checks changed and you didn’t change them. After 12 quiet runs in a row, Crevio can make a frequent job cheaper and tells you what it changed. See a job that keeps finding nothing.
• A job says “Reconnect” and did only part of its work. An app it uses has a broken connection. Reconnect it under connected apps. See when a connected app needs reconnecting.
• A recurring job turned itself off and notified you. It failed several times in a row, so Crevio stopped dispatching it. Open it, check the run history for what broke, fix the cause, then turn it back on.
• Not sure what a job will do? Use Test run — Crevio does the work and shows you what it would have sent, without sending anything. Or set the job to “just suggest” so it shows you its plan without acting.

​

Related