Botski.
The meeting ends. The work moves forward.
A platform connecting meeting intelligence, customer relationships and AI-assisted follow-up. TIN is building the application around the work that happens after a conversation.
Launching soonMeeting intelligence · AI workflows
A useful conversation should leave something useful behind.
Meetings contain decisions, promises and context that are easy to lose between a recording, someone’s notes and the customer record. Botski connects those pieces so the next action can carry the meaning of the conversation with it.
TIN’s scope reaches beyond generating a summary. It includes meeting workflows, a customer workspace, configurable AI assistants and the operational controls needed to offer the platform to separate teams.
The experiences inside the platform.
Team application
Meetings, customer records, tasks and assistants.
Operator console
Workspace plans, entitlements and usage.
Background services
Meeting processing, scheduled jobs and connected tools.
Meeting context connects with the customer record and the work assigned to the team.
Inside the platform.
Keep the context with the meeting.
The meeting workflow brings calendar scheduling, capture, transcripts and recordings together. Summaries surface decisions and action items so a team can return to the substance without replaying the entire conversation.
Calendar changes matter too. The application reconciles changes to meeting times and processes capture events, keeping the meeting record connected to what actually happened.
Connect the conversation to the customer.
Contacts, companies, deals and tasks give the meeting a business context. A follow-up belongs with a relationship and an owner, rather than remaining an isolated item in a transcript.
The wider application includes a shared inbox and team access. TIN is building these connections into the product so meeting intelligence can participate in everyday customer work.
Give AI a job, and define its limits.
Configurable assistants combine instructions, connected tools and scheduled jobs. Approval steps are part of the design for actions that need a person’s decision before proceeding.
Usage budgets and tool permissions belong alongside the assistant itself. Teams need to know what an assistant may access, what it can do and when a task should pause for review.
One product, separate team boundaries.
TIN built the application layer and integrated meeting-capture, transcription and AI services behind it. Team data is separated at the database level, while operator permissions are distinct from ordinary workspace access.
Incoming integration events are verified before processing. Background jobs manage longer-running work, and usage accounting connects assistant activity to plan entitlements and spending limits. Those controls make the business model part of the platform architecture.
Preparing the first release.
Launching soonBotski is launching soon. Meeting intelligence is the initial focus, supported by the customer and operational workflows described here.
The first release is centred on carrying meeting context into decisions, assigned tasks and customer follow-up, with team access and usage controls built around that work.