Start with the workflow, then let Relayne keep your place.

01 · Getting started

Begin with one repetitive Windows workflow.

Relayne is easiest to evaluate when the source, destination, expected values, and current manual process are specific.

1. Choose a task you repeat often enough to measure.
2. Identify the source documents or applications.
3. Identify the destination form, document, or portal.
4. Decide whether AI Powered is permitted or premium Local is required.
5. Use non-sensitive test data during onboarding unless the workflow has been explicitly approved.

02 · Windows permissions

Grant only the access explained by the current build.

Relayne needs Windows access to read selected sources, understand the active destination context, and position the popup. The exact permission prompts depend on the shipping implementation and will be documented before download.

• Read every permission explanation before accepting.
• Use Windows settings to review or revoke access.
• End the Relayne task when the source should no longer be available.
• Report any behavior that appears broader than the selected workflow.

03 · Choose sources

Tell Relayne where it may look.

A source can be a selected PDF, browser tab, email, spreadsheet, document, or supported application surface.

1. Open the sources needed for the task.
2. Add only the relevant sources to the active Relayne workflow.
3. Check that the correct files or tabs appear in the source list.
4. Remove sources that are no longer needed.
5. Return to the destination application and begin with a known field.

04 · Hidden sources

The source does not need to stay beside the destination.

After a source is selected, it can remain behind the window where you are working. Relayne keeps the relevant task context so you can use the destination at a comfortable size.

• Do not close a source if the active build requires it to remain open.
• Minimize or place the source behind the destination.
• Tab through the destination fields normally.
• Use the popup’s source action when you need to inspect the original context.

05 · The Relayne popup

Relayne stays small and field-side.

The popup appears beside the active destination field or writing context. It is not a separate accounting, CRM, or document application.

• Suggestion: the likely value or passage from a selected source.
• Following: Relayne is comparing the current entry as you type.
• Match: the entry matches the selected source value.
• Difference: the entry does not match and needs review.
• View source: return to the relevant source and context.

06 · Multiple sources

Use the active field or sentence to narrow the right source.

When several sources are selected, Relayne can use the destination context to decide which source is most relevant.

1. Select the documents and tabs that belong to the same task.
2. Use clear source names where the build allows it.
3. Continue in the destination form or document.
4. Review which source Relayne selected for each suggestion.
5. If the wrong source appears, reject the suggestion and report the context that caused the confusion.

07 · Processing modes

Choose accuracy or on-device privacy before the task begins.

AI Powered and Local use different data paths.

• AI Powered: Relayne-controlled model infrastructure for maximum recognition accuracy on irregular layouts.
• Local: selected source content is processed on the Windows device without a cloud document-processing dependency.
• Trial rule: premium Local is not included in the private-beta trial.
• All modes: customer content is not used to train models and customer data is not sold.

Read the full current architecture and unresolved implementation details on the security page.

08 · Troubleshooting

Start with the source, destination, and active context.

When the popup does not show the expected result, capture enough information to reproduce the behavior without sending real customer data.

• Confirm the intended source is selected and still available.
• Confirm the destination field or document is active.
• Check whether the application and version are part of the supported beta workflow.
• Record whether AI Powered or Local was selected.
• Use synthetic or redacted examples when reporting the issue.
• Include the Windows version and Relayne build identifier.