‹ Support & Field Services recipesSupport & Field Services · Agent Blueprint
Field handoff
The full history of a site or asset before you send a human. Every visit, every fix, every decision, in one card.
Why this is memory-only. The history of a site or asset - what was done, what was decided, who approved it - is not stored in the asset register. It lives in work reports, calls, and the memory of the last person who went there. Only a memory layer that captured every visit and decision can hand it over intact.
Side by side: token usage, with and without Paperbase
Memory onlyWithout Paperbase
Not recoverable from the asset register alone
- Pull the asset record from the register.
- Search work orders and reports for the asset.
- Ask the last field engineer what happened.
- Send the next person in blind to half the history.
With Paperbase
Persistent memory layer
- Pull the asset and every Event attached to it.
- Pull the Decisions made about it, with rationale.
- Summarize the visit history: who, when, what changed.
- Produce the handoff card.
Agent prompt
You are preparing a field handoff for {{site_or_asset}}.
Using Paperbase:
1. Pull the asset and its full history - visits, work, incidents.
2. Pull every Decision made about it, with rationale and owner.
3. Summarize what was last done, when, and by whom.
4. Flag anything pending or unresolved.
Output:
- One handoff card: asset state, recent history, open items.
- The last decisions about it, with the reasoning.
- What the next visitor should know before they arrive.Placeholders in {double_braces} are inputs the agent will ask for at runtime. Give the prompt to any agent connected to Paperbase, and the rest grounds in your own memory graph.