Private, DM-based legal intake
Legal requests often contain sensitive information such as home addresses, compensation details, or contract terms. Instead of routing these requests through a public Slack or Teams channel, Console supports direct message intake.
Users can message the Console bot directly, or use a /help command from anywhere to start a private conversation. Requests are routed through direct messages with the bot, ensuring sensitive information isn’t exposed in shared channels.
Because Console integrates with identity providers, it has a real-time understanding of who the end user is, including their role, department, and permissions. This ensures that sensitive legal requests are handled in the correct context and only accessible to the appropriate parties.
Dedicated legal workspace with strict isolation
Legal operates within its own dedicated workspace inside Console, separate from IT, HR, or other departments.
Each workspace includes:
Its own knowledge base
Its own automations, called playbooks
Its own ticket queue
Workspace-level isolation ensures legal tickets remain private. HR cannot see IT tickets, and IT cannot see legal tickets.
Admins from other teams can be granted an “integrator” role within the legal workspace. This role allows them to configure settings without being able to read individual legal tickets or conversations.
This permission model addresses a common concern in traditional systems where administrators either have full access or none at all.
Automated intake and contract workflows
Legal teams can use Console’s playbooks feature to build automated intake flows in natural language.
For example:
A contract request can automatically prompt the user for required fields
The selected contract type, such as NDA or purchase agreement, determines which workflow is triggered
Console collects intake information such as counterparty name and contract type, then routes the request to the appropriate workflow automatically.
Ironclad integration
Console integrates with Ironclad to create and manage contract records.
After collecting intake information from the user, Console can:
Automatically create the correct record in Ironclad
Trigger the appropriate Ironclad workflow based on contract type
For functionality not yet natively supported, Console’s custom actions feature can call Ironclad API endpoints directly.
Users can also ask for status updates such as “What’s the status of my Ironclad request?” Console retrieves the latest update from Ironclad on demand.
Automatic triage and routing
When a user sends a message, Console analyzes the context and determines which workspace, such as IT, legal, or HR, is most relevant.
If the correct workspace cannot be determined automatically, Console prompts the user to select the appropriate team.
This allows legal teams to avoid maintaining a dedicated intake channel. Employees can simply message the bot, and Console routes the request to the right workspace behind the scenes.
Once routed, the request remains locked to that workspace unless cross-workspace routing is explicitly configured on the backend.
Current state of feature maturity
At the time referenced in the source discussion, some elements, particularly deeper Ironclad sync and custom field support, were still being built out.
Legal teams adopting these features would be early adopters working alongside product as the integration matured.
Subscribe to the Console Blog
Get notified about new features, customer
updates, and more.