# Town Work assistant for email, calendars, documents and recurring team workflows. Canonical profile: https://ki-agentenkompass.de/en/agents/town/ Editor: [Michael Meierhoff](https://ki-agentenkompass.de/en/about/) Sources reviewed: 2026-10-16 Basis: provider documentation. Examples are editorial suggestions, not hands-on product tests. ## Overview Town: separate product profile from the personal-agent research. - Provider: Town - Product family: Town - Profile type: Personal agent - Environment: App and connected services - Connections: Connections listed under features - Setup: Create an account and connect required work services. - Pricing model: Complete public pricing unconfirmed in the reviewed sources. ## Key features ### Prepare email Draft messages and send with permission. Source: https://www.town.com/docs/getting-started ### Coordinate schedules Handle calendar tasks and scheduling. Source: https://www.town.com/docs/getting-started ### Use documents Include documents in work tasks. Source: https://www.town.com/docs/getting-started ### Research the web Gather external information for a task. Source: https://www.town.com/docs/getting-started ### Share routines Use recurring workflows and team context. Source: https://www.town.com/ ## Example workflows ### Editorial starter task - Your input: Draft a reply to a scheduling email with two calendar options. - Possible result: A reviewable draft with open questions and the inputs used. - What to check: Compare the result with the inputs; approve external actions only after personal review. ### Example: Coordinate appointments - Your input: A bounded task for “Coordinate appointments” with approved sample data. - Possible result: Handle calendar tasks and scheduling. - What to check: Compare the result with the inputs; approve external actions only after personal review. ## Requirements and limits ### Access Requirement: Create an account and connect required work services. Source: https://www.town.com/docs/getting-started ### Specific boundary Limitation: Connected accounts and action permissions determine executable scope. Source: https://www.town.com/docs/getting-started ### German and reliability Not yet confirmed: German interaction and success rates have not been tested hands-on here. Source: https://www.town.com/docs/getting-started ## A good fit if … - you want an assistant with its own email address for email, calendar and Drive - you want to start routines by schedule, email, calendar event, Slack mention or webhook - you want to set roles in a team and decide per integration who may use it ## Less suitable if … - you want to pay with a non-US card, as some such cards fail at checkout - you need team routines with approval before every action; they always run automatically Editorial assessment based on provider documentation. Not a product test. ## Usable AI models Fixed choice across providers Town picks the model per task itself: Anthropic is the primary provider, with OpenAI and Gemini for selected features. The pages checked describe neither a model choice nor your own keys. - Model families named: Anthropic (Claude), OpenAI (GPT), Google (Gemini) - Model choice: The product chooses - Your own API key: Not stated - Router or custom endpoint: Not stated - Local models: Not stated Documented · Sources accessed on: 2026-11-05 - [Town: AI Model Providers](https://www.town.com/ai-model-providers) - [Town: Subprocessors](https://www.town.com/subprocessors) - [Town: Product](https://www.town.com/product) - [Town: Updates](https://www.town.com/updates) ## Europe & regional availability Original sources reviewed; specific country availability remains unresolved. Reviewed scope: Product access, channels and regional evidence Reviewed on: 2026-10-19 ### Europe: specific availability unconfirmed Availability still unclear According to the page, paid billing is not yet available everywhere, and some cards issued outside the US can fail at checkout. If the bank requires extra verification, Town cannot currently walk you through that step. The page gives no country list for Europe. Region covered: Germany, EU/EEA, United Kingdom and Switzerland Documented reason: The reviewed sources identify no regulatory reason for a regional restriction. Official source: https://www.town.com/docs/billing/cancellation-and-refunds ## Accounts & permissions Based on provider documentation. Permissions depend on the account, integration and organization policies. Review the permissions actually requested before use. Configuration covered: A person's Town assistant, individual or within a team workspace Sources reviewed: 2026-11-05 ### Account used Documented: When you sign up, you name your assistant and get a dedicated email address at town.com. It uses connected accounts such as Google or Outlook through your connection; OAuth tokens are stored securely and refreshed automatically. Installable routines run with the identity of the respective member, background routines as the team. Evidence: https://www.town.com/docs/getting-started Evidence: https://www.town.com/docs/teams Evidence: https://www.town.com/docs/safety/security ### Admin approval Documented: The roles are Owner, Admin and Member. By default admins and owners control who creates installable routines and skills and who invites members. For each integration you can choose who may use it: all members, specific members or team routines only. The reviewed pages do not mention admin rules for approving individual actions. Evidence: https://www.town.com/docs/teams Evidence: https://www.town.com/docs/safety/modes-approvals ### Data access & team sharing Documented: The assistant only reaches accounts you have connected; routines can be limited to the triggering account, all connected accounts or selected accounts. Team integrations are shared: every member with access can reach whatever the connection can reach in that tool. Evidence: https://www.town.com/docs/safety/security Evidence: https://www.town.com/docs/teams ## Prices and included usage Pricing checked: 2026-10-16 Complete public pricing unconfirmed in the reviewed sources. Pricing reflects reviewed sources; confirm unlisted amounts and access with the provider. Pricing details: https://www.town.com/docs/getting-started ## Operation & oversight Based on public provider documentation. Assessments are editorial inferences from the stated properties. Actual time requirements and reliability have not been measured. Deployment covered: Hosted service with routines, triggers and team workspace Sources reviewed: 2026-11-05 ### Files and working state Open in reviewed sources: The reviewed pages do not describe how sandbox state or files are stored between runs. Evidence: https://www.town.com/docs/safety/security ### Sign-ins Documented with conditions: According to the documentation, OAuth tokens are stored securely and refreshed automatically. What happens on expiry is not stated. You can disconnect accounts at any time in your account settings. Evidence: https://www.town.com/docs/safety/security ### Starting further runs Documented: Routines start manually, on a schedule, on new emails, calendar events, transcribed voice recordings, Slack mentions or via authenticated webhook. According to the Teams page, a free team cannot run background routines. Evidence: https://www.town.com/docs/routines/custom-routines/triggers Evidence: https://www.town.com/docs/teams ### Human intervention Documented: Per thread you choose Auto, Balanced or Strict, and per tool Ask each time or Always allow. Routines run in Auto or Human in the Loop mode, where actions other people would see wait for your approval; team routines always run in Auto. Evidence: https://www.town.com/docs/safety/modes-approvals ### Detecting errors Documented with conditions: Every action is logged with its time, reasoning, trigger and result; the result is recorded as success or failure. The security page does not describe automatic reporting of failed runs. Evidence: https://www.town.com/docs/safety/security ### Resuming after failures Open in reviewed sources: Recovery after failures is not described. For approvals, the session stays paused until you answer in the chat; Dismiss only clears the notification and neither approves nor rejects. Evidence: https://www.town.com/docs/safety/modes-approvals ### Editorial assessment Triggers, approval modes and the action log are well documented, whereas state, failure reporting and recovery are not. For teams this means setting roles and integration access deliberately. ## Memory and conversation continuity Scope: Personal Townie across web, Mac, Slack and email Sources accessed: 2026-11-04 Global and routine-specific memories with profile view and chat controls. ### Storage and scope Partly documented: Town keeps role, people and preference information in a readable profile view. Backend and file format are not named. - [Context & Memory](https://www.town.com/docs/features/context-and-memory) - [What is Town?](https://www.town.com/docs/getting-started) ### Selection and timing Documented: Style and key facts are mostly learned automatically; explicit instructions are classified as global or routine-specific memories. - [Context & Memory](https://www.town.com/docs/features/context-and-memory) - [What is Town?](https://www.town.com/docs/getting-started) ### Inspect, edit and delete Documented: Settings → Profile shows memories and allows deletion; review questions and forgetting requests also work through chat. - [Context & Memory](https://www.town.com/docs/features/context-and-memory) - [What is Town?](https://www.town.com/docs/getting-started) ### Agent and channel boundaries Documented: The same personal memory follows web, Mac, Slack and email. Global entries apply everywhere; routine entries apply to the relevant routine. - [Context & Memory](https://www.town.com/docs/features/context-and-memory) - [What is Town?](https://www.town.com/docs/getting-started) ### Retrieval Documented: Each routine run automatically receives global and matching routine-specific memories. The Townie makes the selection. - [Context & Memory](https://www.town.com/docs/features/context-and-memory) - [What is Town?](https://www.town.com/docs/getting-started) ### Session reset and compaction Partly documented: Memory survives routine runs and channel changes. Technical context compaction and a separate session reset are not explained. - [Context & Memory](https://www.town.com/docs/features/context-and-memory) - [What is Town?](https://www.town.com/docs/getting-started) ## Context Connected accounts and action permissions determine executable scope. Provider sources reviewed; the following examples are editorial suggestions, not hands-on tests. ## Open points Europe, availability still unclear: - Europe: specific availability unconfirmed Requirements and limits, not yet confirmed: - German and reliability ## Sources - https://www.town.com/docs/getting-started - https://www.town.com/ ## Provider Provider of Town; identity and features documented through linked sources. - Operator: Town - Organization: Provider - Website: https://www.town.com/docs/getting-started - Reviewed: 2026-10-16 - Provider source: https://www.town.com/docs/getting-started - Provider source: https://www.town.com/ [Sources and method](https://ki-agentenkompass.de/en/sources/)