Inbox & proposals

AI proposes; a person decides

The Inbox is a private staging queue for unstructured football information. Relai reads email, text, files, screenshots and voice notes, then turns useful facts into separate proposals. A proposal is a candidate CRM action, not a draft record and not an automatic change.

One capture can produce several independent proposals, such as a deal, contact and task. You review and decide on each one. A processed capture with no proposals is also a valid result: it means Relai found nothing actionable enough to suggest.

Several inputs share one review boundary

Every capture channel enters the same basic sequence: preserve the source, extract facts, create pending proposals and wait for a human decision. The channel label tells you where the item originated; it does not change the approval rules.

Forwarded email

Send a useful thread to the workspace address from the email on your member account.

Typed or pasted text

Add a quick note or paste source text directly into the Inbox capture box.

Images and files

Paste a screenshot or drop an image or PDF. Relai reads the source conservatively and retains it for review.

Voice

Record a note in the app. The recording is transcribed before the same extraction and review process runs.

The Inbox is personal; accepted work is shared

You see only the inbound emails, app captures, attachments and proposal history submitted by your account. Another member of the same workspace does not inherit your review queue, so the Inbox should not be treated as a shared team mailbox.

When you accept a proposal, the resulting deal, note, contact, contract, task or signal becomes normal workspace-visible CRM data. The raw source, transcript and pending, accepted or rejected proposal rows remain private to the submitting member.

Inbound email must pass two checks

The recipient address must resolve to the intended workspace, and the From address must match the account email of a current member of that workspace. Matching is case-insensitive, but aliases and secondary mailboxes are not accepted unless that exact address belongs to a member.

Unknown workspace addresses and unverified senders are stored as ignored diagnostics and never sent to the extraction model. If a forwarded email never appears, first check the workspace forwarding address and the exact sender address on your account.

Common Gmail, Outlook and Apple Mail forwarding formats are recognised. A note written above the forwarded thread is separated from the original message so both the instruction and underlying source can be considered.

Statuses describe the source pipeline

Inbox filters group items that need review, are still processing, failed, or have finished. Source status and proposal status are separate: a Processed item can still contain several Pending proposals.

Received

The capture is safely stored and waiting for processing to begin.

Processing

Relai is reading the source and preparing structured suggestions.

Processed

Extraction finished. There may be proposals to review, or nothing actionable may have been found.

Ignored

An inbound email failed workspace routing or sender verification and was not sent for extraction.

Failed

Processing exhausted its automatic retries; the source and error are retained.

Proposals are typed create or update operations

Each proposal names the object it affects and whether acceptance will create something new or update an existing record. Keeping the suggestions separate lets you approve the useful parts of a source without accepting the whole extraction as one bundle.

Evidence matters more than confidence

A proposal card shows its structured facts, a confidence score and the exact source quote used as evidence. Confidence expresses how certain the extraction was; it does not prove that a fact is commercially correct or current. Compare names, clubs, dates and values with the source before deciding.

If a player name cannot be matched confidently, select the correct registry player or create a new prospect. Unresolved proposals cannot be bulk-approved. Proposal fields cannot currently be edited inline; reject an inaccurate suggestion and create or update the correct record manually.

Pending

The suggestion has not changed the CRM and is waiting for your decision.

Accepted

The proposed create or update has run through the normal domain rules.

Rejected

No CRM change was made; the suggestion and optional reason remain in the history.

Acceptance crosses into the shared CRM

Accepting runs the same domain validation and audit events as a manual action. A deal, contact, contract, task or signal is created through its normal service; a player note is appended to the player timeline; a supported contract update changes its existing record.

You can accept proposals individually or select several ready proposals. Each acceptance runs independently, so one failure does not roll back the proposals that succeeded. Open the resulting record afterward and add any assignment, stage, due date or commercial detail the source did not supply.

When an accepted proposal concerns a resolved player, retained source attachments are also linked into that player's documents. The original capture remains private even though the resulting document link and CRM record are shared.