Morning inbox review
- Runs
- every day, 06:30
- Reaches for
three company sources- Leaves
- draft replies to review
Done before anyone asked
Routines work in the background all day and leave the result ready. All you do is review it — nothing goes out to a customer without your approval.
06081012141618
06:30every day Inbox review Four replies waiting to be reviewed
Inbox review Four replies waiting to be reviewed 08:12an email arrived Zenit — complaint #4821 Triaged, owner assigned, reply drafted
Zenit — complaint #4821 Triaged, owner assigned, reply drafted 09:15before the meeting 
Pre-call brief Kamex, 9:30 — brief ready
Pre-call brief Kamex, 9:30 — brief ready 11:30file in the Quotes folder Quote for Nowak Checked against the price list — two lines to fix
Quote for Nowak Checked against the price list — two lines to fix 13:40stage changed in CRM 
Terms summary Kamex — PLN 16,200, PLN 13,770 net after discount
Terms summary Kamex — PLN 16,200, PLN 13,770 net after discount 17:00every day 
End-of-day summary Three cases are stuck — posted to #sales
End-of-day summary Three cases are stuck — posted to #sales That was not one morning.That is every morning.
The same week, zoomed out. Every bolt is one run at its own hour. The clock or the bolt next to a name says what fires it — and you can see at once that some come back on schedule while others come back when something happens.
Inbox review every day, 06:30 5
Email replies an email arrives 23
Pre-meeting brief 15 minutes before 9
Terms for negotiation stage changed in CRM 4
Rollout review every Monday, 07:00 1
0 runs in a single week. Nobody asked for a single one — and nobody had to remember them.
You write a sentence.appto arranges the rest.
There is no wizard, no branches, no conditions to click together. You describe in a sentence what should happen — and that sentence has exactly three parts.
When a new email from a customer arrives,
Trigger
An hour or an event in your tools. It is the only thing you have to point at.
check the knowledge base for what it is about and draft a reply in our tone,
Task
The same thing you would ask a person to do. The routine reaches for company context and connected tools.
but leave it for review.
Boundary
Nothing goes outside without your approval. Changing that is a separate decision.
Not one routine.A dozen in every team.
A routine is not a feature you switch on once. You set one up as often as something comes back around — and it comes back everywhere. Below are the ones teams usually start with — a few from each of six departments.
Sales
Lead summary for the Monday review
every Monday, 07:00
Terms for a deal that entered negotiation
stage changed in CRM
A brief before every customer meeting
15 minutes before
and 9 more in this team
Customer service
Draft replies to whatever landed in the inbox
an email arrives
Triage a ticket and assign an owner
new ticket
Cases with no reply for 48 hours
every day, 09:00
End-of-day summary of open cases
every day, 17:00
and 11 more in this team
Operations
Check a quote against the price list on upload
file lands in the folder
Orders above the approval threshold
new row in the sheet
Review of rollouts that are stuck
every Monday, 07:00
and 8 more in this team
People
Welcome pack for a new joiner
new row in the sheet
Reminder about contracts running out
first day of the month
Summary of time-off requests
every Friday, 15:00
and 6 more in this team
Finance
Invoices unpaid past their due date
every day, 08:30
Cost summary for the monthly close
last day of the month
A flag when a cost exceeds the team budget
new row in the sheet
and 7 more in this team
Leadership
Week in review for Monday morning
every Monday, 07:00
Matters stuck for more than two weeks
every Monday, 07:15
Board decisions sent out to the teams
the meeting ends
and 5 more in this team
Set up your first routine
The template goes to the team.In one click.
A routine that worked for you becomes a template. You share it with the team and everyone has it — nobody rewrites it, and sharing opens none of your documents to anyone.
It does not stop at text.It goes into your systems.
Monday, 07:00. Nobody clicked. The routine reads from Drive, changes state in the CRM and leaves the result in Slack — on the same permissions as the person it works for.
Starts
Every Monday, 07:00
Nobody clicks. An hour you set yourselves.
Reads Google Drive
Takes the price list and the rollout status sheet — today’s version, not a copy.
Changes HubSpot · CRM
Updates the stage on two deals and assigns an owner according to your procedure.
Leaves Slack · #sales
Drops the summary where the team already is on Monday morning.
Automation had to be built.A routine only has to be described.
Firing on a trigger is not new. What is new is that you no longer have to click out every condition, field and exception up front — or maintain them afterwards.
Without appto · scenario
Trigger new email Sender filter one list Condition subject contains Branch A four steps Branch B two steps Field mapping 12 Templates three languages Retries 3, then alert Call limit 40 per hour After the run log and label
With appto · routine
“When an email from a customer arrives, check the knowledge base for what it is about and draft a reply in our tone. Leave it for review.”
Start with Monday
One routine on the task you do the same way every Monday. With the result left for review — you see the difference after a week.
No card. Your account takes 30 seconds.
Before you set up the first one
The questions people ask about work that happens without them. Not sure where to start? We will walk through your Monday with you and point at the first routine.
Will a routine send something to a customer without us knowing?
Not unless you set it up that way. A prepared trigger starts switched off — you turn it on deliberately. By default a routine ends with a result to review, not with an action taken outside. Moving to sending without approval is a separate decision and a separate setting.
What does a routine see in our data?
Exactly as much as the person it works for. A routine operates within their permissions — it will not see a folder, a channel or a record they cannot open. Changing someone’s permissions immediately changes the reach of their routines.
How does a routine know what matters to us?
From the same place as the rest of appto: your company context and your connected tools. A routine going through the inbox uses your procedures and your price list, so what it proposes is not generic — it is yours. That is why routines come after knowledge and integrations, not before.
Who can create and change routines?
A routine fired by a trigger is created, edited and archived by an admin or a manager. That way work happening in the background for the whole team does not change by accident.
Where does the result land?
Where you work: in appto, in a Slack channel or in Microsoft Teams. A routine’s report arrives in the place you are in anyway in the morning, instead of waiting in yet another system.
How many routines should we start with?
One — ideally the one about Monday morning, because that is where the difference is easiest to notice. Once it runs and the team stops mentioning it because it is simply there, add the second.