Relayora

Help and tutorials

Build a small test, check the result, and know which operations need a live provider.

Learn the workflow before your pilot

These guides explain agent setup, knowledge, workflow tests, and action review. Use sample data while learning. Public account registration is not open yet.

Provider-backed calls and messages require a separately configured pilot. The examples below do not activate them.

Local setup

Create your first agent and workflow

Define a small job and save the conversation rules.

  1. Use the workspace access provided by your operator. Public account registration is not open in this private pilot.
  2. Open Agent studio. Create an agent, name its job, and write the questions it should handle. Say when it should ask for a person.
  3. Open Workflows. Create a call-workflow simulation, add message and decision steps, and connect each path to an end.
  4. Save the draft, choose Validate, then Publish. Return to the agent and select the published workflow.
What to expect

You have a saved agent and published call-workflow simulation. This does not activate a live phone number.

Local simulation

Test a conversation and record feedback

Check expected paths before trying a real model or voice channel.

  1. Open Test playground and select the agent you want to check.
  2. Enter a sample customer message and choose Run simulation. Read the transcript and workflow events.
  3. Try the handoff, opt-out, and instruction-attack fixtures. Run the four regression cases to check the defined paths.
  4. Choose Review & leave feedback. Record what needs to change, then edit the agent or workflow and test again.
What to expect

Simulation results are saved locally. They do not establish real model quality, live call latency, or protection against every attack.

Local retrieval; model tests gated

Add knowledge and check source matches

Give the agent business information you can review.

  1. Open Knowledge and choose Add a source. Paste text or import a .txt or .md file. Add a clear source title.
  2. Save the source. Use Preview retrieval to search a likely customer question and inspect the matching passages.
  3. In Grounded chat, choose Configure model & sources. Select only the documents that this agent should use.
  4. Keep supporting evidence required when answers must come from those documents. Sending to a model needs separate operator access and credentials.
What to expect

Local search calls no model. Source URLs are labels, not crawled pages. The pilot does not import PDFs or automatically verify answer accuracy.

Local steps work without a provider

Publish and run a local automation

Run a versioned process and inspect each step.

  1. Open Automations and choose Create automation. Start with Local input example or Support routing example.
  2. Review the graph JSON and save the draft. Choose Validate, then Publish to freeze a version.
  3. Choose Run, select a published version, and enter the manual input JSON. Review the exact version and input before submitting.
  4. Read the saved run trace. Model steps require live runtime access. An action draft pauses the run for separate review.
What to expect

These automations execute real local steps. They are separate from call-workflow simulations. Manual runs do not create a schedule.

Local review; execution gated

Review an email, calendar, or WhatsApp draft

Check the exact action before it can leave the workspace.

  1. Open Action approvals and choose Draft an action.
  2. Enter the recipient and content, or the event and time zone. Record the actual consent reference and applicable purpose.
  3. Save the draft. Review the exact payload and choose Approve exact action only when it is correct.
  4. Execution is a separate control and remains disabled until the operator has configured access. An uncertain outcome needs receipt review, not a replacement request.
What to expect

Saving or approving a draft sends nothing. Drafts expire. A confirmed provider receipt is needed before claiming the action succeeded.

Local permission ledger

Record consent and respect an opt-out

Keep a customer address separate from permission to contact it.

  1. Open Contacts and add an email or phone identity. Creating it does not grant permission.
  2. Open its permissions and record an actual grant or revocation. Include the channel, purpose, evidence reference, source, and capture time.
  3. A revocation suppresses the channel. A later grant leaves that suppression in place.
  4. Reinstatement requires a fresh grant after suppression and an explicit review of the current suppression record.
What to expect

The ledger stores operator-supplied evidence. It does not independently prove lawful consent. Deletion preserves hashed suppression safety records.

Operator setup; no automatic activation

Understand provider setup and access gates

Know why a live control is unavailable before changing anything.

  1. Open Integrations and read the server-reported status. Selecting an integration is a saved preference, not a completed connection.
  2. Workspace text-model keys, when enabled, are stored encrypted and unverified. This does not configure voice, phone carriers, payments, or OAuth.
  3. Read the disabled-control reason. Credentials, workspace allowlists, consent, provider configuration, and any subscription gate can each block a live operation.
  4. Billing is a separate setup surface. Opening it does not purchase a plan. Do not proceed to live checkout or provider tests during a local demonstration.
What to expect

Adding a key or reviewing setup makes no provider inference call. Only the operator should enable a controlled live test after the required checks.

Local data controls

Export or delete workspace customer data

Understand what is removed and what safety records remain.

  1. Open Settings, then Data controls. Download a workspace JSON export if you need a review copy.
  2. Read the deletion scope before confirming. It includes saved conversation and action content, automation run payloads, and contact details and evidence.
  3. Contacts are suppressed before their details are deleted. Hashed safety records prevent deletion from silently restoring contact permission.
  4. Workspace configuration, knowledge sources, published definitions, and audit or safety receipts have separate retention. Backups and provider-held data need their own process.
What to expect

Deleting local data does not reverse a sent message, end a provider operation, or delete every copy held elsewhere.

Common questions

Why is Send to model or live calling disabled?

Local demo mode blocks provider activity. Outside demo mode, the operator must configure the provider, allow the workspace, and satisfy the relevant operating gates. Read the reason shown by the control.

Why did publishing not change a previous run?

Published automation versions are immutable. A run records the version it used. Publish a new version and start a separate reviewed run to test a change.

Can I retry after a timeout?

A timeout does not establish that the provider did no work. Use the retained request and receipt controls. Do not change its operation key or create a replacement until the outcome is reviewed.

Does saving a provider key verify it?

No. The key is stored encrypted and marked unverified. Saving it does not test model access or confirm the provider account.

Why is a recreated contact still suppressed?

Deletion removes identity and evidence content but keeps hashed safety records. Recreating the same address does not erase its opt-out history.