Trigger
A run starts when something arrives: an email, a form, a calendar change or a set time.
One run, from trigger to result.
Every job in Sparvek has five parts. Each one leaves a line on the receipt.
Agent
One specialist takes the job. It works inside its own list of tools and hands off when its part ends.
Tools
The agent uses the tools you already run. Each connector says what it may read, draft and do.
Controls
Anything that leaves the building stops for a person. The run waits for as long as you take.
Result
The run ends with what changed: a meeting on the calendar and one updated record.
A handoff passes the whole story.
- What was askedThe original request travels with the run, word for word.
- What was decidedEach agent notes what it concluded and why.
- What is still openThe next agent starts from the open item, not from zero.
What a receipt records.
Four lines, on every step, in every run.
Who actedThe agent by name, or the person who approved.
Which tool ranInbox, calendar or CRM, with the scope it used.
Receipt 4127-0308:41:12
- Who
- Bastien, Scheduling
- Tool
- Calendar
- Did
- Held Thu 12 Nov, 14:00
Paused for your approval
What happenedOne plain sentence, written as the step ran.
What came of itThe result, or the reason the run stopped.
The same morning, with a record of it.
Without Sparvek
- The lead sits in a shared inbox until someone claims it.
- Two people answer, or nobody does.
- The CRM says what someone remembered to type.
- When it goes wrong, you ask around.
With Sparvek
- Odile reads it first and says what it is.
- One agent holds the job, and one person answers.
- Wren writes down what changed, when it changed.
- When it goes wrong, you read the receipt.
What sits around the run.
Everything a small team needs to hand over a queue and keep an eye on it.
Every run, searchable
Find a client, a tool or a date and read what happened.
5
Parts, always
Trigger, agent, tools, controls, result. Every run reads the same way.
Handoffs you can point to
One agent passes the job to the next, in writing.
Runs on a schedule
Set a time for the jobs nobody triggers by hand.
One workspace
Your team sees the same queue and the same receipts.
We stopped asking who picked up the lead. The run says who, when and with what.
