From installation
to your first answer.

BEFORE YOU INSTALL

Prove it on your team’s work.

Start with one team, a few approved sources and questions you can check. A suggested evaluation is 5–10 people over two weeks. Agree availability, any usage allowance and support with your rollout contact before installation; this plan is not a commercial trial offer.

1. Choose one recurring problem.

   Start with release blockers, a current policy question or a thread follow-up. List the source content and destinations your admin has approved, and decide what a useful answer must contain.

2. Check the evidence and the boundaries.

   Ask a question with a known answer and open the cited source. Try the same question with a teammate who has different access. Ask about something undocumented and check that Ashoon identifies what it cannot verify.

3. Measure the work that remains.

   Record whether answers were useful, how long checking or correction took, and whether people came back in week two without a reminder. Compare with their existing workflow. Investigate access problems immediately; any unauthorized disclosure stops the evaluation.

Download the evaluation scorecard ↓

The scorecard is a blank Markdown worksheet for your own approved workspace. Downloading it submits no information. Choose your success criteria before starting, then decide whether to continue, change the scope or stop.

FOR THE INSTALLING ADMIN

Set up your workspace.

Have someone who can approve Slack apps and authorize the source connection complete these steps.

1. Install in the right Slack workspace.

   Choose your company’s workspace and review the requested permissions. If approval is required, ask your Slack workspace admin. Each workspace configures its own sources and member access.

2. Open your private setup link.

   Use the setup link on the installation success page and sign in with Slack as the installing account. The eligible installer becomes Ashoon’s first admin. To reopen setup later, send admin in a direct message to Ashoon, then choose Get started.

3. Connect and test one source.

   In Connect, choose a source, save its settings and service credentials, and enable it. In Test, run the connection test. You do not need to connect every tool. A passed connection test checks connectivity; your first question will also exercise content access and retrieval.

4. Allow your teammates to use Ashoon.

   In Members → Access, set the allowed company email domains or have an admin link members individually. Until member access is configured, installation alone does not enable every employee. Guests and external Slack accounts cannot use company answers.

   For channel use, approve the channel in Ashoon’s admin console and add Ashoon to it in Slack. Start in a DM if you do not need channel answers yet.

5. Ask and check a real question.

   DM Ashoon about information you know exists in the connected source. Open its citations and compare the answer with the source. Give Helpful / Not helpful feedback when available. Check access and answer quality with a small group before expanding.

MICROSOFT TEAMS

Use Ashoon in Teams too.

Teams supports cited answers, approved actions and scheduled questions with the same source access checks. Colleague messaging, handoffs and living-document workflows currently use Slack. A company can use both: people keep one Ashoon workspace.

1. Already using Ashoon in Slack?

   An Ashoon admin connects Microsoft 365 with Connect with Microsoft on any Microsoft source. This confirms your Microsoft 365 organization: its verified domains must match the workspace’s allowed email domains. Then open Products → Chat platforms and choose Enable Microsoft Teams.

2. Add the Ashoon app in Teams.

   A Teams admin adds the Ashoon Teams app to the teams and chats where it should answer. The Teams app store listing is not available yet: your Ashoon contact provides the app package to upload as a custom app, if your Teams admin allows custom apps.

3. Only on Teams?

   Arrange the rollout with your Ashoon contact before adding the custom app. Adding the app or sending its first message can currently create a workspace for an unlinked Microsoft organization. The eligible person who adds the bot becomes its first admin. Your rollout contact should verify this account and Microsoft sign-in setup before inviting employees. Then configure Members → Access and connect one trusted source.

4. Ask in Teams.

   Message Ashoon in a 1:1 chat, or mention it in a channel thread where it is installed and the channel is approved in Ashoon’s admin console. Guests and people from other organizations get no company answers.

FOR EMPLOYEES

Ask where you already work.

Open Ashoon in Slack’s Apps list and send start in its Messages or Chat tab for a short guide. Send help for available commands.

Ask about a source your admin has connected and that you can read. For example:

• “Where is our current time-off policy? Include its source.”
• “What are the open blockers for our next release?”
• In an approved channel: “@Ashoon summarize this thread and list the agreed next steps.”

Use a DM for your first question. In approved channels, mention @Ashoon. Follow up in the same thread to clarify or correct the answer; to stop a task that is still running, press Stop on its status card.

Answers depend on both your access and the people who can see the response. A channel may receive less detail than your DM. Check citations before relying on an answer; tell Ashoon when something is missing or incorrect.

RECURRING WORK

Your schedules, under your control.

Create a scheduled question in chat, for example schedule daily 09:00 in me: What changed in our release project?. Schedule times use UTC. Sources and destination access still apply to every run.

Open My workflows and sign in with Slack or Microsoft to review your own scheduled questions and living documents. Pause, resume, or change a supported schedule there. New workflows and instruction changes start in chat.

Living documents currently start from Slack and can be published as an Ashoon page, Slack canvas, Confluence page, Notion page or Google Doc when that destination is configured. An Ashoon page’s link requires sign-in and current reader access.

WHEN SOMETHING NEEDS ATTENTION

Find the next step.

GET HELP

Keep the right person in the loop.

Employees: contact your workspace’s Ashoon admin for connection and access issues. Admins can use the console’s task state and audit information to investigate. During a pilot, escalate unresolved issues through the person who arranged your rollout.

Share the task reference, what you expected, and the time of the problem. Keep credentials, private answer text and personal admin links out of shared support conversations.