A guided look at Synconaut · example walkthrough · nothing here is saved
SYNCONAUT.A Speed & Co. product
Synconaut astronaut

Guided demo

Vendor documents multiply fast. The chasing should not.

Follow two common missions: annual vendor renewals and event COIs. See the requests, who replied, who went quiet, what came back, and the moment a human takes over.

01 · Configure

You set the rules first.

Recipients come from your vendor list. Your templates, timing, renewal windows, and follow-up rules are reviewed before the first message goes out.

People

Your vendor list

Your vendors, the people on your team who handle issues, and where flagged items should go.

Messages

Your message templates

Outside-party language is approved before first use and populated with the details your team supplied.

Rules

Timing and follow-up rules

Renewal windows, follow-up timing, and the point where silence stops with a human.

Example rosterCustomer supplied
VendorDocumentExpiresInternal owner
Beacon ElectricCOIAug 18Procurement
Northside LandscapingCOIAug 22Public Works
River Tent & StageEvent COIEvent dateEvents
City SoundEvent COIEvent dateEvents

02 · Annual renewals

A different clock for every vendor.

Synconaut starts the agreed request before each expiration date, records the reply or silence, and follows up inside the customer’s rules.

RequestFollow upReceiveHuman review
What happened next: Beacon replied with the document. Northside stayed silent past the configured limit, so the item stopped with the internal owner.

03 · Event vendor COIs

One event, many vendors, one compressed clock.

The event lead supplies the participating vendors and the due date. Synconaut runs the same request and follow-up across the whole list.

Summer concert · COI missionEvent date: Sep 12
VendorStateLast action
River Tent & StageWork in motionPromised by Friday
City SoundReceivedDocument logged today
Main Street CateringSilentFlagged to event lead
First Aid PartnersLoggedReady for human review
No one-to-one onboarding ritual: the value comes from handling a full renewal or event list, not from turning each new vendor into a separate project.

04 · Receive

What arrived is a fact, not a verdict.

Synconaut records what arrived and flags anything that looks off. It does not turn a document into a final answer.

Received

City Sound

The COI arrived and was logged. It is ready for the event lead to review.

Needs attention

Pine Valley Lawn Care

The attachment is too blurry to read. Synconaut requests a clearer copy.

In motion

River Tent & Stage

The vendor replied with a Friday promise. The follow-up clock pauses until then.

Received or loggedWork in motionFailed, silent, or needs attentionHuman-confirmed status only

05 · Human review

The short list is where people earn their keep.

A human sees the few items that need context or judgment. Green appears only after that person confirms the status.

Mission summaryEmail-ready
VendorCurrent stateHuman next step
Beacon ElectricHuman confirmedNo further action
Northside LandscapingSilentInternal owner decides whether work pauses
Pine Valley Lawn CareUnreadableWait for clearer copy
City SoundReceivedEvent lead reviews
Synconaut tracks, requests, and flags. Your team decides what is enough.

06 · Safety

Clear boundaries.

The follow-up can move quickly because the boundaries are clear.

No mailbox access

Forward only what matters

Synconaut does not receive credentials that let it browse a customer inbox.

No document storage

Originals stay with you

Your email and record systems remain the source of truth.

No final decisions

Hard cases stop with people

Unreadable files, silence, and questions route to the responsible human.

Outbound communication stays under customer control: the customer sets the people, messages, timing, renewal windows, and when something comes back to a person. Synconaut runs follow-up inside those rules.

Mission complete

Every vendor. Every paper. Handled.

The requests move, the states stay visible, and the decisions remain with your team.

Demo questions

Where do recipients come from?

From your vendor list. Synconaut never contacts anyone you have not added to your list.

Does every message need separate approval?

No. The customer approves the templates and agreed rules before use. The follow-up then runs inside those rules.

What happens when a vendor works through an agent?

The customer can set the vendor as the main recipient and the agent as a copied contact. A reply from either ends the silent status.

What happens when a document is unreadable?

Synconaut flags the problem and requests a clearer copy. It does not guess.

Who decides whether a document is enough?

The responsible person at the customer organization.

Where are records stored?

The source documents stay in the customer’s own mailbox and record systems. Synconaut scans each document, pulls out what matters, discards the working copy, and keeps only a pointer back to the source.

What happens if Synconaut goes away?

The chasing pauses. Records do not disappear. The customer’s email, documents, and legal records remain exactly where they already live. An interruption never becomes a loss of custody.