What is StoriBot
StoriBot connects to the systems your business already runs on and does two jobs.
- It drafts the files and reporting pages a team rebuilds by hand. The board pack, the monthly report, the client update. Drafted from your own systems, in your template and your language, with every number traced to its source.
- It does the task someone carries between two systems. The work done with two tabs open: read it here, make sense of it, enter it there. StoriBot reads both ends the way a person would, so there is no field mapping to build first.
Anything that costs someone three hours a week qualifies.
How you use it
Section titled “How you use it”You talk to StoriBot in the app. Tell it what you want made or done. It asks what is missing, sets up a Stori, builds it, and gives you the link. When you come back, it picks up the Stori that fits rather than starting another.
What a Stori is
Section titled “What a Stori is”A Stori is the durable thing your organisation keeps, not a one-off page. It always has a page, and the page is often the face of something else: a Word document needed every quarter, a report rebuilt each month from live systems, a task that moves data between two systems. Each one is set up to run again: the data it reads, the file it produces, the job that runs it.
What a Stori makes is a file in your own template (Word, PowerPoint, Excel), a live page your team works from, or an email. Anything it makes can be shared with the people you choose.
What is in the app
Section titled “What is in the app”- Stories. Every Stori in your organisation.
- Library. What your organisation gives StoriBot: skills, rules, agents, presets, memory, and its voice and brand reference files.
- Team. The members of your organisation and their roles.
- Jobs. What StoriBot runs on a schedule, as the person who made it.
- Integrations. The systems you have connected, and exactly what StoriBot may do with each one.
- Settings. Security policies, billing and email for your organisation.
The rules it works under
Section titled “The rules it works under”Reads are the default. Every write is one you granted, one operation at a time, and one switch in Settings turns every write off. StoriBot runs in its own cloud environment in AWS Sydney. The full list of controls is at stori.bot/trust.