Context in SlackYour workspace's agents in Slack
Ask your agents where you already talk
Mention Context in a Slack channel and it works the task in your workspace, with your files and your permissions, and brings the result back to the thread.
Tested end to end against a Slack test workspace, ready for your first install. Talk to us
IC is Friday 10:00. Agenda: Q2 attribution, the Hallam refinancing, pipeline.
Overnight Snowflake refresh finished, the Q2 attribution rows are current through Tuesday.
@Context compile the Q2-to-date attribution package for Friday's IC. Writeup plus the underlying numbers in one place.
@Context compile the Q2-to-date attribution package for Friday's IC. Writeup plus the underlying numbers in one place.
IC is Friday 10:00. Agenda: Q2 attribution, the Hallam refinancing, pipeline.
Overnight Snowflake refresh finished, the Q2 attribution rows are current through Tuesday.
@Context compile the Q2-to-date attribution package for Friday's IC. Writeup plus the underlying numbers in one place.
@Context compile the Q2-to-date attribution package for Friday's IC. Writeup plus the underlying numbers in one place.
Ask in the channel
Mention Context in a bound channel and the workspace's agent picks up the task, answering in the thread.
Get the files back in the thread
The writeup and the numbers come back as links to files the task wrote in your workspace's Drive.
Decide before anything leaves
A step that leaves the thread waits for the person who asked or a channel owner to approve it.
Work the task from the thread
The ask, the progress and the result stay in the Slack thread where the work was discussed.
@Context compile the Q2-to-date attribution package for Friday's IC. Writeup plus the underlying numbers in one place.
Pulling the Q2 attribution rows and the factor scorecards now; the writeup and the numbers come back here as one package.
@Context compile the Q2-to-date attribution package for Friday's IC. Writeup plus the underlying numbers in one place.
Pulling the Q2 attribution rows and the factor scorecards now; the writeup and the numbers come back here as one package.
Results land in your workspace
The work happens in Context, so the files, the task and the channel's history are kept where your team can govern them.
Install it in one sitting
The connector opens an outbound connection to Slack, so nothing on your side needs a public address or an ingress change.
Secure by default
The person who asked is the one the agent acts for, steps that leave the thread wait for a decision, and every delivery is on the record.
Pick the work up anywhere
A task started in Slack is the same task in the web app, on your phone, on your Mac and in the terminal, under the same account and permissions.
Review is Thursday. Priya, can you get the portfolio pack started? Same structure as Q2, and Northwind and Alder go in the risk section this time.
@Scout pull the Q3 updates for all 14 portfolio companies from the data room and flag anything more than 10% off plan.
Three companies moved more than 10% against plan: Northwind Logistics (revenue down 14%, one lost contract), Alder Health (up 18%, the payer contract started early) and Fenwick Tools (EBITDA down 11%, freight). Sources are linked in the doc.
@Ledger rebuild the valuation bridge with the Q3 actuals and rerun the covenant tests for Northwind and Fenwick.
Northwind passes leverage at 3.9x against a 4.5x covenant. Fenwick's interest cover is 2.1x with the test at 2.0x: passing, but tight. One tab per company in the workbook.
Review is Thursday. Priya, can you get the portfolio pack started? Same structure as Q2, and Northwind and Alder go in the risk section this time.
@Scout pull the Q3 updates for all 14 portfolio companies from the data room and flag anything more than 10% off plan.
Three companies moved more than 10% against plan: Northwind Logistics (revenue down 14%, one lost contract), Alder Health (up 18%, the payer contract started early) and Fenwick Tools (EBITDA down 11%, freight). Sources are linked in the doc.
@Ledger rebuild the valuation bridge with the Q3 actuals and rerun the covenant tests for Northwind and Fenwick.
Northwind passes leverage at 3.9x against a 4.5x covenant. Fenwick's interest cover is 2.1x with the test at 2.0x: passing, but tight. One tab per company in the workbook.
The workspace behind the thread
Slack carries the ask, the replies and the decision. Context carries the task, the files, the permissions and the record.
- TogetherThe workspace's own chat, where a bound Slack channel is mirrored.
- DriveWhere the files a task writes are saved, with the same sharing as every other file.
- SkillsThe instructions the agent follows when it works a task from Slack.
- Secure VMEach task runs in its own sandbox under the permissions of the person who asked.
Home
- q3-portfolio-review.pptx1h ago
- q3-valuation-bridge.xlsx2h ago
- q3-portfolio-updates.docx3h ago
- lp-letter.pptx5h ago
Home
- q3-portfolio-review.pptx1h ago
- q3-valuation-bridge.xlsx2h ago
- q3-portfolio-updates.docx3h ago
- lp-letter.pptx5h ago
Deploy in your environment
The connector runs where your workspace runs, hosted, in your own cloud or on-premises, over an outbound connection to Slack.
- Runs where your workspace runsThe connector is part of your Context deployment, hosted or in your own cloud.
- Outbound connection onlyIt connects out to Slack over Socket Mode, with no public URL and no ingress change.
- Tokens stay in your deploymentThe Slack app's tokens are set in your deployment's configuration, one Slack workspace per deployment.
- Your identity providerSign people in with SAML or OIDC and provision them with SCIM, then link Slack with /ctx connect.
- Your own cloud
- On-premises
- Slack
Context in Slack is included in every Context workspace, including the Free plan.
- Free$0Includes Context in Slack
- Plus$20Per person per month
- EnterpriseCustomEnterprise deployments run in your own cloud.Talk to us about a plan
Questions
Who is it for?
Teams whose work is already discussed in Slack, such as deal teams, finance operations, legal operations and support, where the result needs the firm's files and a person's review.
Where does the work happen?
In your Context workspace. The task runs there with its steps, tools and files, and Slack shows its status, the replies and the links.
Whose permissions does the agent use?
The person who asked, once they link their Slack account with /ctx connect. An unlinked sender is a guest with no grants, and a turn without a credential is refused.
Can the agent share a file without asking?
No. Anything that leaves the thread waits for the person who asked or a channel owner to approve it, with the buttons or a reaction, and the message records the decision.
Does it need a public endpoint?
No. The connector opens an outbound Socket Mode connection to Slack, so there is no public URL and no ingress change.
Is it available today?
The connector is tested end to end against a Slack test workspace. Talk to us to plan your first install.