ashoonAdd to Slack

AI assistant for Slack & Microsoft Teams

Ask once.
Your team keeps moving.

Ashoon answers your team’s questions in Slack and Microsoft Teams, using Jira, GitHub, your docs and the other tools you connect, with the sources attached.

Add to Slack Plan a pilot

Early access · Admin-led setup. Installation starts no paid subscription. See company credits · Using Microsoft Teams?

Example: asking what’s blocking a release

#release-room · Maya

@Ashoon what’s blocking the billing release?

Jira · BILL-142Migration ready
GitHub · PR #87Fix not merged
ConfluenceRollback: no owner
Two blockers, one unknown.

Merge PR #87 and give the rollback checklist an owner.

Unverified: no deployment record found.

JiraGitHubConfluence

Illustrative product examples · fictional sources

Your tools

Bring the tools
you already use.

Your admin connects the sources that matter, tests each one and decides who can use it. Open a tool to see what it needs.

Availability depends on your deployment, source permissions and configuration.

In your chat

Three things Ashoon
does in your chat.

DM Ashoon or mention it in an approved channel. Follow up in the same thread, and stop a running task from its status card.

Illustrative product examples.
Source names and content are fictional.

release-room

Maya

@Ashoon What’s blocking the billing release?

Ashoon APP

Company sources checked · Shared only with an allowed audience

Two blockers, and one thing we cannot confirm.

  • Jira marks the migration ready, but its GitHub fix is still unmerged.
  • The rollback checklist needs an owner.
  • Deployment evidence is missing. Release readiness is unverified.
Jira · BILL-142GitHub · PR #87Confluence · Release checklist
Inspect the answer’s sources
Jira · BILL-142

Migration · Status: Ready

Checked 09:41 UTC · Example revision 12
GitHub · PR #87

Migration fix · Status: Open, not merged

Checked 09:41 UTC · Fictional pull request
Confluence · Release checklist

Rollback checklist · Owner: Unassigned

Checked 09:41 UTC · Example version 4

Fictional source records for this demo, not live company data.

Sources included. Follow up in the same thread.

release-room

Maya

@Ashoon Draft an update for the release channel.

Ashoon APP

Destination and content reviewed before sending

Here’s the proposed update. You decide what gets sent.

  • Billing release: migration review is pending.
  • Next step: assign a rollback checklist owner.
Draft for #release-roomApproval required
Preview what you would approve
Destination · #release-room

Billing release update: the migration review is pending. We still need an owner for the rollback checklist.

Example only. Nothing is sent from this website. In Slack, you review the exact action before approving it.

Review the draft → Approve the exact action → Send

Ashoon · direct message

Maya

@Ashoon Create a canvas for #release-room: open release blockers. Keep it updated every morning.

Ashoon APP

Document access follows its intended readers

A living release brief, with a clear owner and schedule.

  • A Slack canvas for the approved readers.
  • Scheduled refreshes, source checks, and version history.
Slack canvasDaily · 09:00 UTC
Explore the living brief
Billing release · Open blockers

Owner: Maya · Readers: approved release-room audience

Refresh: daily at 09:00 UTC · Example version 3

The document keeps its sources, readers, and version history. Its owner can pause refreshes or roll back a version.

Pause, update, or roll back from the conversation.

What your team gets

From “I wonder”
to “it’s handled.”

One assistant for the context your team needs and the work that follows. Start with a question. Build from there.

01 · Knowledge

Your company,
with the dots connected.

Ask about a decision, a release or a customer issue. Ashoon brings the relevant sources together, with citations, versions and checked times you can trace.

02 · Actions

Help that moves
work forward.

Turn context into a draft or a proposed action. You review the exact content and destination before a supported write.

03 · Living documents

A brief that
keeps itself fresh.

Create a page, Slack canvas, Confluence or Notion page, or Google Doc with its readers and refresh schedule. Living-document workflows currently use Slack.

04 · Automations

Recurring work,
on a rhythm.

Schedule questions and reusable skills with set tools, destinations and budgets. Pause, resume or retime them in My workflows.

05 · Teamwork

The right person,
at the right time.

Draft messages to colleagues and hand blocked work to an owner. Colleague messaging and handoffs currently use Slack.

06 · Memory

Know what changed.

Ask “what changed this week?” and see the recorded edits, owners and sections you can read. Updates depend on each source and its connection.

A day with Ashoon

Five moments you know.
One question each.

The questions you chase across tools every day, asked once where you already work: Slack or Microsoft Teams. Explore each moment. Example content is fictional; the “without” steps describe a typical manual workflow.

  1. Slack · DM

    Catch up before stand-up

    Without Ashoon

    • Open Confluence page history
    • Scan Jira for updated issues
    • Ask the team in #billing

    3 tools or people to check

    With Ashoon

    “What changed in Billing since yesterday?”

    Two edits and one access change.
    • Refund policy · section “Partial refunds” rewritten by Lena
    • BILL-142 moved to Ready
    • Pricing FAQ is now visible to Support
    Confluence · Refund policyJira · BILL-142

    1 question · answer in the thread

    Company memory records source changes and only shows what you can read.

  2. Teams · chat

    Answer a policy question

    Without Ashoon

    • Search the wiki and get 40 results
    • Open the old and the new policy
    • Check which one is current

    2 tools or people to check

    With Ashoon

    “How many vacaton days carry over?”

    Up to 5 days carry over to next year.
    • From the current policy, not the 2023 version
    • Understood the typo and quoted the exact section
    Confluence · Leave policy › Carry-over

    1 question · answer in the thread

    Finds the right paragraph, understands typos and your company’s acronyms.

  3. Slack · #release-room

    Check if a release can ship

    Without Ashoon

    • Open the Jira issue
    • Find the linked pull request
    • Read the release checklist
    • Ping two engineers

    4 tools or people to check

    With Ashoon

    “Can we ship the billing release?”

    Not yet: two blockers, one thing unverified.
    • Jira says ready, but the GitHub fix is unmerged
    • Rollback checklist has no owner
    • No deployment record found
    Jira · BILL-142GitHub · PR #87Confluence · Release checklist

    1 question · answer in the thread

    Pulls code, tickets and docs together, and says what it could not verify.

  4. Slack · thread

    Turn the answer into an update

    Without Ashoon

    • Copy notes from three tools
    • Write and format the update
    • Double-check the facts

    3 tools or people to check

    With Ashoon

    “Draft the update for #release-room.”

    Here’s the draft. You approve before it’s sent.
    • Billing release: migration review pending
    • Next step: assign a rollback owner
    Approval required

    1 question · answer in the thread

    Drafts actions for you. You review the exact draft before this action is sent.

  5. Slack · DM

    Never write that update again

    Without Ashoon

    • Repeat the 12:40 search tomorrow
    • And the day after

    Every day, by hand

    With Ashoon

    “schedule daily 09:00 in #release-room: What are the open release blockers?”

    Scheduled. Every day at 09:00 UTC.
    • Same sources, refreshed each morning
    • Pause, resume or reschedule in My workflows
    Schedule · Daily 09:00 UTC

    1 question · answer in the thread

    Recurring work runs on a schedule, with an owner and limits.

YOUR TIME BACK

How much of your week goes to finding things?

Put in your own numbers. The estimate uses only what you enter; the starting values are an example, not a measurement of Ashoon.

Your team
Looking things up
Status updates and catch-ups

5.8hours back per person, every week
249hours back for the team, every month
31.18-hour working days a month

Weeks of 5 working days, months of 52/12 weeks. Estimated capacity, not guaranteed savings; rollout and checking time are not included. Shown for the example values; with JavaScript off, the numbers don’t update.

Trust & control

The right answer.
For the right audience.

Company knowledge has boundaries. Ashoon treats them as part of the job.

See how access and approvals work

Access comes with every answer.

Source access is checked for the person asking and for the people who will see the response. Private context stays in the appropriate conversation.

Sources you can actually follow.

Citations, versions and checked times show where an answer came from. When something can’t be verified, Ashoon can withhold it or hand it off.

Real control for your admins.

Manage connectors, approved channels, members, projects, retention and audit activity. Disable a connector when you need to stop new calls.

Actions stay accountable.

Supported writes require approval. Scoped identities, task history, budgets and audit records make the work inspectable.

Start small

Your first useful answer
starts with your workspace.

Install it for one team, connect one source and check the answers against your own systems before you expand.

  1. Add Ashoon to Slack.

    Choose your workspace and review permissions. Open the private setup link and sign in with Slack as the installing admin.

  2. Connect one trusted source.

    Save and test the connection. Configure member access, then approve the channels where Ashoon may answer.

  3. Ask a real question.

    DM Ashoon about content you can read. Open the citations, check the answer and follow up in the same thread.

Plan a pilot

Prove it on your team’s work.

Start with one team, a few approved sources and questions you can check. The setup guide has a pilot plan and a blank evaluation scorecard.

Read the pilot plan

Company credits

$100 10,000 credits

One shared balance for your company, visible to your admins. This is an example package only: online purchases and automatic usage charging are not live yet, and installation starts no paid subscription.

Understand pricing and credits

Start with one
real question.

Install as a workspace admin, connect a trusted source and ask the question your team keeps asking.

Add to Slack Plan a pilot

Good questions

A little context
before you start.

What happens after installation?

Your admin opens the private setup link, connects and tests a source, and configures member access. Employees then DM Ashoon or mention it in an approved channel. Each workspace connects its own tools. Follow the setup guide for admin and employee instructions.

Does it work in Microsoft Teams?

Yes. Teams supports cited answers, approved actions and scheduled questions with the same source access checks. A company can use both platforms. Colleague messaging, handoffs and living-document workflows currently use Slack. Your admin turns Teams on for the workspace and adds the Ashoon Teams app; a Teams app store listing is not available yet. See Teams setup.

Can everyone see the same answer?

Not necessarily. Ashoon checks access for the requester and the destination audience. An answer in a channel must be suitable for the people who can read it; fuller private context can be delivered in a DM when allowed.

Can Ashoon change things in our tools?

Supported actions can be proposed for human approval. Availability depends on the connector, its permissions, and your admin configuration. Scheduled documents have explicit owners, readers, and configured write destinations.

How is Ashoon priced?

Your company shares a credit balance for Ashoon usage, visible to workspace admins. Credits are not raw tokens or a fixed number of answers. Online purchases and automatic usage charging are not live yet. See pricing examples and early-access details.

Where can I manage recurring work?

Open My workflows and sign in with Slack or Microsoft. Review your own scheduled questions and living documents, pause or resume them, and change supported schedules. Create new workflows in chat.