Pilot support
Typical response within 24 hours for pilot users.
Pilot support
Support and trustfor approved project sources
Lyqa keeps pilot users grounded to selected Slack project channels, shows where project context comes from, and gives a clear support path when evidence or processing needs attention.
Lyqa reads selected Slack project channels approved for this pilot. Direct messages, unapproved channels, and unsupported sources stay out of scope.
What Lyqa reads
Selected Slack project channels only
Approved sources stay project-bound, traceable, and narrow enough for a pilot user to understand.
- Selected Slack project channels approved for this pilot.
- Project-bound evidence references tied back to approved sources.
- Registered file sources only when they are explicitly configured for this workspace.
What Lyqa does not read
Direct messages stay out of scope
Pilot v0 does not quietly widen source scope behind the scenes.
- Direct messages (DMs).
- Unapproved Slack channels outside the project scope.
- Private data outside configured pilot sources.
Data handling
Evidence remains traceable
Support guidance should stay accurate, short, and customer-safe instead of leaning on unsupported security claims.
- Generated insights link back to approved project sources whenever evidence is available.
- Data is managed according to the pilot retention policy.
- Deletion requests are handled through the pilot support process.
- File source registration is optional and is not auto-ingested in Pilot v0.
Pilot support
Know where to go next
Use project views for health, and use support contacts when access, privacy, or evidence availability needs help.
Security contact
Use for access, privacy, or data handling questions.
Trust surface
Privacy, data handling, and approved source scope live here.
Status surface
Operational status and incidents should stay separate from the product UI.
Project-specific processing health, last refresh status, and evidence coverage belong inside Setup, Project Leader, Team Leader, and Evidence Q&A. This page stays focused on scope, trust, and recovery guidance.
Where to look next
Project-specific health stays inside the workspace
These routes carry the live project view. Support stays customer-safe and explains how to recover when a source or answer needs attention.
SetupReview approved Slack sources, invite access, and project-specific processing health.Project LeaderFollow up on decision context that needs action today and keep updates grounded to approved evidence.Team LeaderSee only escalation-worthy context, evidence coverage, and recommended intervention.Evidence Q&ACheck a question against approved Slack evidence before sharing a project answer.
Reusable support patterns
Customer-safe empty and error states
These components are designed to drop into Setup, Project Leader, Team Leader, Evidence Q&A, Invite, and Sign In without exposing internal diagnostics.
Setup and source states
Connect only approved project sources
These states belong in Setup when Slack access, channel membership, or early processing is incomplete.
Setup state
Action neededNo approved Slack source connected
Lyqa cannot process project conversations until an approved Slack project channel is connected for this pilot.
Only selected Slack project channels are in scope. Direct messages and unapproved channels are not read.
Use Setup to connect the approved channel for this project, then confirm the bot is invited before asking Lyqa to refresh context.
Setup state
Action neededBot not invited to the channel yet
The approved Slack channel exists, but Lyqa cannot read project messages until the bot has been invited.
Invite the bot only to approved project channels. Direct messages remain out of scope.
A healthy source binding still needs channel membership before messages can be processed into conversation units and decision context.
Processing state
Expected stateNo messages processed yet
Lyqa has an approved source, but it has not processed any project messages for this workspace yet.
Processing begins only after approved Slack project channels have usable activity for this project.
This is expected for a newly connected project or a quiet channel. Review processing health in Setup if the source has recent activity.
Project and evidence states
Stay calm when evidence is thin or context is stale
Project Leader, Team Leader, and Evidence Q&A should guide the user without exposing raw diagnostics.
Decision context state
Expected stateNo decision context detected yet
Lyqa processed approved project messages, but it did not find a decision-ready signal that needs follow-up right now.
This is a quiet project state, not a failure. Evidence remains bounded to approved Slack project sources.
Project Leader and Team Leader views can stay calm when no escalation-worthy context appears in the latest processed material.
Decision context state
Action neededProject context is stale
The latest approved Slack activity is newer than the decision context currently shown in the workspace.
Review processing health before sharing a summary when the last refresh is behind recent project traffic.
A stale context warning should prompt a refresh check, not an unsupported answer. Keep follow-up grounded to approved evidence.
Evidence review state
Action neededInsufficient context for a safe answer
Approved project sources do not yet contain enough evidence for Lyqa to answer this question safely.
Lyqa should ask for clarification or show what evidence is missing instead of guessing beyond approved sources.
Use this state when a question goes beyond the current project-bound Slack evidence or when references are too thin to support a grounded answer.
Evidence review state
BlockedEvidence is unavailable right now
This answer references project evidence that is not currently available in the approved source view.
Treat this as a temporary evidence access problem, not as permission to answer without traceable support.
Use customer-safe copy here and keep internal logs or stack traces out of the workspace surface.
Processing state
BlockedLatest refresh did not complete
Lyqa could not finish the latest processing run for this project.
Review Setup first, then contact pilot support if the same failure repeats after the approved source looks healthy.
This state should never expose raw stack traces. Keep diagnostics concise and customer-safe unless an operator opens a deeper tool.
Auth and access states
Keep invite and sign-in recovery clear
Invite recovery should explain the next step without sending the user through a maze of separate error pages.
Access state
BlockedThis invite has expired
Ask your Lyqa pilot admin or support contact for a fresh invite link before trying to enter the workspace again.
Expired invites should be calm and clear. They should not imply that direct messages or unapproved channels were ever in scope.
Returning users should use Sign In after access is accepted. Invite variants stay bounded to first-time access and access recovery.