Skip to main content

Source Material, Email, And Files

Relay works best when source material includes the problem, users, scope, constraints, goals, success criteria, open questions, and any relevant prior decisions.

Supported intake sources include:

  • Slack messages and threads.
  • Slack files.
  • Inbound email body text.
  • Inbound email attachments.
  • TXT files.
  • JSON transcripts or generic JSON.
  • DOCX documents.
  • PDF documents.
  • XLSX spreadsheets.
  • PPTX slide decks.

Use Slack when source context is already in a conversation. Use inbound email for longer briefs, forwarded customer conversations, external partner context, or files that are easier to send by email.

Inbound Email​

Each team has an inbound email address based on its ID prefix, for example:

ENG@intake.relay.app

Relay routes inbound email in this order:

  1. If the recipient local part is an initiative ID, such as ENG-123@intake.relay.app, attach the email to that initiative.
  2. If the recipient local part is a team prefix, such as ENG@intake.relay.app, Relay looks for an initiative ID in the subject or body.
  3. If no initiative can be matched, the email is recorded as unmatched and is not attached to an initiative.

Recommended subject format:

ENG-123 - customer resend context

Email bodies are stored as source artefacts. Attachments are stored and text-extracted when the file type is supported.