Capture data and know-how
Turn scattered spreadsheets into Apps, write your veterans' know-how into Skills, and install them on the Agents that need them.
Turn scattered spreadsheets into Apps, write your veterans' know-how into Skills, and install them on the Agents that need them.
Your Agent is on the job. Now turn your data and know-how into assets that stay.
Customers and quotes live in scattered spreadsheets. Know-how lives in people's heads. Both should be company assets.
Only the person who fills it in understands it.
Finding what was decided takes forever.
No one else can see it or pick it up.
When they leave, the know-how goes with them.
Example: "Follow-ups stay under five lines" goes in memory. "How to chase a quote silent for 7 days" becomes a Skill. Each quote is a record in an App.
One-line preferences and context.
A process with steps.
Business records, one by one.
Example: a senior rep leaves, and their deals and methods stay. A new rep can ask the Agent on day one which deals to pick up.
What it does, who it's for.
Open the preview and click through.
Reply, or click Annotate.
Choose who can open it.
Test records in a draft don't carry into the live version. Actions that touch outside services still run for real in preview. More: kylon.io/help/build-an-app
Example: after watching the recording, the Agent proposes three tables: customers, quotes, follow-ups. The sales lead says, "Drop industry for now."
Once it's settled, have the Agent build it. More: kylon.io/help/choose-app-fields
Put them in a Room. Every member sees them.
Files stay put. The Agent reads them in place.
Hand the sheet to an Agent and it builds the App.
Up to 1 GB per file. More: kylon.io/help/bring-existing-work-into-kylon
Example: the quote tracker lives in the Sales Room, and only Sales Room members can open it.
Anyone with the link: opens without signing in. More: kylon.io/help/build-an-app
Example: a rep says in the thread, "Maple Kitchen replied, meeting Thursday, log it," and the quote moves to Meeting set.
The Agent updates the record.
An Automation in the same Room updates on schedule.
Open the App and edit the record.
Data edits take effect immediately. Only App layout changes go through a draft. Automations come in Lesson 5.
Example: the owner asks the Sales Agent in the Sales Room, "Where did last quarter's lost quotes stall?"
Where did last quarter's lost quotes stall?
I checked 12 lost quotes and their threads: 7 stalled on price, 3 on lead time, 2 had no follow-up.
You can also have it export records to CSV or Excel. More: kylon.io/help/export-app-records
More: kylon.io/product/skills
Research, reports, slides, ready to go.
Have the Agent publish it for the whole workspace.
Upload an existing Skill and it's ready to use.
More: kylon.io/product/skills
More: kylon.io/product/skills
Anything a veteran teaches a new hire can become a Skill.
The same report every week, done the same way.
Which leads go to sales.
How drafts are reviewed before sending.
The checks every delivery must pass.
Example: the sales lead says in the Sales Room, "Follow up on the Maple Kitchen quote," and the Sales Agent works through four steps.
Finds the process for this task.
Sees where the quote stands.
Writes a draft and waits for you to send.
Once sent, it updates the status.
Example: on day one a new rep asks the Sales Agent, "What should I learn first?" and gets a brief built for their role.
New hires must be added to the right Rooms first to ask about what's inside.
The company from Lesson 2: sales, ops, finance, and the owner.
Then fill in the next two pages.
The one that drives revenue and gets asked about most.
The one only one or two people know.
Which Room for the App? Which Agent for the Skill?
Who updates it when things change?
| Spell out | Notes | Example: Quote tracker App |
|---|---|---|
| What it tracks | What this App follows | e.g. Quote follow-up |
| What one record is | What a row represents | e.g. One quote |
| Fields | Start with the fewest | e.g. Customer, amount, next follow-up, owner, status |
| Status options | Define each one | e.g. To quote, following up, meeting set, won |
| Which Room | Where the work is discussed | e.g. Sales |
| Who can open it | Room members only by default | e.g. Sales Room members |
The example is a template. Swap in your own sheet, then send the whole spec to an Agent to build.
| Spell out | Notes | Example: Quote follow-up |
|---|---|---|
| What this process is called | One line anyone understands | e.g. Quote follow-up |
| When to use | When to use it | e.g. A quote silent for 7 days |
| Steps | In order, one line per step | e.g. Check the record, draft a follow-up, log the next date |
| Common mistakes | Past corrections | e.g. Emails too long, next follow-up not logged |
| Which Agent | Who does this work | e.g. Sales Agent |
| Who maintains it | Who updates it when the process changes | e.g. Sales lead |
More: kylon.io/help/bring-existing-work-into-kylon kylon.io/help/build-an-app kylon.io/help/choose-app-fields
An App holding your business data,
and a Skill installed on an Agent.
Agents, Skills and Apps linked into a workflow that runs every week.