Routines
Creating a routine
Two ways a routine starts: Gini offers one after it notices a repeat, or you write one yourself.
Two routes. The first is better, and it's the one you'll use most.
Let Gini offer
Do the job a few times by asking for it. When Gini notices the repeat, it offers to take it over: in the channel, at the end of a run, naming the schedule it's proposing.
Say yes and it's running. Nothing else to configure.
This is the better route because the routine inherits a run you've already read and approved. You know what the output looks like, because you've seen it three times.
Adjust the offer before you accept
"Yes, but Tuesdays." "Yes, and include the EMEA numbers." "Yes, but post it in
#leadership instead." All fine: say it in the thread and Gini creates the
routine you described.
Ask for one directly
If you already know what you want, just say so:
@Gini every Monday at 9, post signups, activation and churn by channel in this channel.
@Gini check every morning for deals with no activity in 14 days and list them here.
@Gini after each customer call, file the action items in Linear and update the HubSpot record.
Gini will confirm what it understood (the work, the schedule, the channel, the tools) before it starts. Read that back properly. A routine misunderstood once is misunderstood every week.
Building one in the web app
Open Routines
app.ginicomputer.com → Routines, and start a new one.
Describe the work
In plain English, the same way you'd ask in a channel. This is the routine's instructions and you can edit it any time.
Set when it runs
A schedule: daily, weekly, monthly, at a time you pick. Check the timezone when Gini reads the routine back to you.
Choose where it posts
Any channel Gini is in, or a DM to you. Pick the channel where someone will actually act on it.
Attach anything it needs
A file, a spreadsheet, a template. Attached files are available to every run of the routine, so you don't have to re-send them.
Run it once
Before you leave it alone. A routine that's wrong on Monday morning in
#leadership is a worse way to find out.
Getting the schedule right
Match the schedule to the decision. A report nobody reads until Monday shouldn't run on Friday: it'll be stale by the time anyone opens it.
Leave room for the data. A month-end report scheduled for 00:01 on the 1st runs before the last day has finished settling. Give it a few hours.
Daily is usually too often. Most weekly things stay weekly for a reason. Daily costs 5× the credits and, more importantly, trains everyone to ignore it.
Test it against a real week
Point a new routine at #gini or a DM for its first run or two. Read what it produces. Then move it to the channel where it belongs.
The failure mode this avoids is a routine that's subtly wrong (right numbers, wrong framing) going out to a room of people who'll assume it was checked.