Bring the systems you already use into your existing AI. Toolcape connects them, while you stay in control of who can do what.
AI tools your team knows
Availability depends on account and company settings.
FROM QUESTION TO ANSWER
«Can we promise Fjordvik a launch on Friday?»
toolcape
SalesforceChecks the case and proposed delivery date
OutlookReads the customer’s meeting recap
Microsoft TeamsFinds the team’s latest test plan
SharePointChecks the agreement’s acceptance criteria
Friday depends on testing and customer approval
Salesforce lists Friday as the proposed date. Export case #84 is still open, with Jonas responsible.
Anne’s meeting recap requires a working export before she can accept the delivery.
Jonas expects the fix to be ready for testing on Thursday. Maria must coordinate verification.
The agreement ties milestone sign-off to an accepted export. A proposed launch date is not enough.
Next step: Prepare a status message for your approval: Friday is tentative until testing passes and Anne confirms acceptance.
MicrosoftGoogleGitHubSlackFikenCloudflare
FOLLOW A QUESTION THROUGH THE SYSTEMS
From scattered information. To a clear next step.
Follow the searches, access checks and sources behind one answer. Scroll or use Next to explore.
FJORDVIK · CUSTOMER FOLLOW-UP01 / 07
Your AIThe question
toolcapeAccess checked
Fiken
Salesforce
Teams
01 / 07
One customer. Three different systems.
“What should we follow up with Fjordvik?” AI needs financial status, delivery status and the latest customer context. Toolcape checks access for each system.
Access before action
Read invoices, cases and messagesAllowed
Create a Salesforce taskSeparate check
Purpose: identify the next follow-up for Fjordvik, as requested by the user.
02 / 07
Start with the financial facts.
AI finds Fjordvik’s customer record and checks invoices and recorded payments. Invoice 1042 is outstanding; a settled invoice is excluded from follow-up.
Customer → invoices → payment status
Fjordvik ASOutstanding invoices
Invoice 1031Settled · no follow-up needed here
03 / 07
Find what is blocking the delivery.
AI searches Fjordvik’s customer account and reads the open export case. Eight of ten cases are closed, but the fix and its verification are still pending.
Fjordvik · open delivery cases
04 / 07
Understand what the customer needs.
Maria’s update links the export problem to the customer’s month-end work. She asks the team to clarify the fix before following up on payment.
Fjordvik delivery team
Maria · customer lead
“Ask Jonas for status before we contact Anne about the invoice. She needs the export for month-end.”
The message connects the delivery case to the customer follow-up.
05 / 07
Connect the findings into a useful answer.
The answer connects finance, delivery and customer context, with a source for each finding. The suggested next step is to get a technical status update first.
Follow this up with Fjordvik
Fiken shows NOK 12,500 outstanding. No payment is recorded.
Export case #84 is open with Jonas. Verification in #85 also remains.
Ask Jonas for status first, then agree the customer follow-up with Maria.
06 / 07
Create a follow-up where the work happens.
You ask AI to create a follow-up task in Salesforce, linked to #84. Review the customer account and content before approving. No customer financial details are copied into the case.
Review before creating
AccountFjordvik AS
TitleFollow up export fix #84
Get a status update from Jonas on #84. Confirm when the export can be tested in #85, and share the proposed date with Maria before she follows up with the customer.
07 / 07
What was created — and why.
The audit trail records the requested operation, its purpose, approval and outcome. Permission to read a customer account does not automatically grant permission to create an case.
A traceable outcome
Action
Create a follow-up task in Salesforce
Stated purpose
Clarify the export fix before customer follow-up
Approval
Not yet approved
Outcome
Waiting · nothing created
FJORDVIK · CUSTOMER FOLLOW-UP01 / 07
“What should we follow up with Fjordvik?”
Your AIThe question
toolcapeAccess checked
Fiken
Salesforce
Teams
Access before action
Read invoices, cases and messagesAllowed
Create a Salesforce taskSeparate check
Purpose: identify the next follow-up for Fjordvik, as requested by the user.
Explore step by step
A SIMPLE START
Simple setup. Full control.
Toolcape brings MCP servers and systems with APIs into one connection for the AI your team already uses.
Decide which actions each person and group may perform, whether the connection uses MCP or an API. The system does not need its own MCP server.
One connection, across your systems
ChatGPT
Claude
Copilot
toolcapeYour access rules
MCP serversExisting AI connections
APIsSystems without their own MCP server
Fiken
Salesforce
Teams
Switch AI. Keep your connections.Moving from ChatGPT to Claude? Connect Toolcape in your new AI client. Your system connections and access rules stay in Toolcape.
Available actions depend on your accounts, permissions and AI client.
01
Connect your systems
Connect an MCP server or configure the system’s API.
02
Set the boundaries
Choose the operations each person and group may use.
03
Use your existing AI
Add Toolcape in a compatible AI client.
YOUR EVERYDAY SYSTEMS
Familiar systems. New possibilities.
Bring accounting, customer follow-up and deliveries into your existing AI. Find the systems you use, then choose the services.
MicrosoftOutlook, Teams & files
Google WorkspaceEmail, calendar & documents
SlackTeam conversations
GitHubCode & projects
FikenAccounting
CloudflareCloud & domains
BRING THE TEAM ALONG
Easy to invite. Clear from day one.
Invite a colleague by email. Decide which systems and actions they can use. Joining the workspace does not automatically grant access.
The administrator grants access. Nora connects her own accounts where required.
YOU SET THE RULES
AI can read. Can it also change things?
An answer may only need read access. Changing a document requires a separate permission. Nora inherits these boundaries from the Sales group.
Nora’s accessSales representative · Sales
Access from group: Sales
SharePointChoose the permitted actions
Read the project planAllowed
Change the project planBlocked
Nora inherits these permissions from Sales. Everyone in the group gets the same group permissions, within their account’s own limits.
YOUR ACCOUNT. YOUR BOUNDARIES.
AI works within your existing access.
When a service is connected through your own account, AI can only use what that account can access — and what the connection and your organisation permit.
Nora’s accountSales · SharePoint
Atlas project planNora can read it. AI may read it too.
Management folderNo access for Nora. No access for her AI.
Allowing all actions in Toolcape does not open the locked folder. Shared accounts and application permissions work differently.
SECURITY & TRACEABILITY
Know what AI does. And why.
See the action, the purpose stated by AI and the result together. Access rules determine what can be carried out, and the audit trail makes incidents easier to investigate.
Security log
Prepare for a customer meeting
Action
Read the delivery plan in SharePoint.
Stated purpose
Prepare for the customer meeting you asked for help with.
Outcome
Completed with read access.
Deletion blocked by an access rule
The account had read access. The file was not deleted.
View the blocked action’s audit trail
Action
Delete an older version of the delivery plan.
Stated purpose
Keep only the latest version, as requested by the user.
AI client
ChatGPT
System
SharePoint
On behalf of
Emil
Access rule
Read only · deletion not permitted
Outcome
Blocked before execution
YOUR NEXT STEP
Make room for a more connected workday.
Join the waitlist. We’ll let you know when Toolcape is ready for you and your team.
An email when early access opens.
A question before you join?
Explore the guides, get a question for your AI, or see how we can help with setup.