Skip to main content
GenosOS includes 12 pre-built templates for common business and operations use cases. Each template defines the agent’s name, purpose, tool profile, channel configuration, connected services, and security hardening. Deploying a specialized agent takes one conversation — no config files, no code.

​
How templates work

Templates are knowledge files, not code. Each template is a Markdown file in skills/agent-templates/templates/. When you ask for a specialist agent, GenosOS:
  1. Identifies the matching template from your description
  2. Creates the agent with config_manage agents create, passing the template slug
  3. The gateway reads the template and applies the full configuration: name, description (injected into SOUL.md), tool profile, allowed tools, denied tools, A2A wiring, and any bundled skills
  4. Reports back what was configured
The entire process is one config_manage call. You do not need to read the template or answer a series of questions.

​
Business templates

A patient-facing assistant for dental offices and medical practices.
  • Channels: WhatsApp + Voice (Twilio/Telnyx)
  • Services: Google Calendar, CRM, Stripe
  • Use cases: Appointment scheduling, service inquiries, payment links, follow-up reminders
A client-facing assistant for legal consultancies.
  • Channels: WhatsApp + Email
  • Services: Google Calendar, CRM, Stripe
  • Use cases: Consultation booking, document intake, billing, client communication
An e-commerce assistant for order management and customer support.
  • Channels: WhatsApp + Discord or Telegram
  • Services: Stripe, CRM
  • Use cases: Order status, product questions, payment links, returns
A front-of-house assistant for restaurants, cafes, and food service.
  • Channels: WhatsApp + Voice
  • Services: Google Calendar, Stripe
  • Use cases: Reservations, menu questions, takeout orders, payment
A property assistant for agencies and independent agents.
  • Channels: WhatsApp + Email
  • Services: Google Calendar, CRM, Stripe
  • Use cases: Property inquiries, viewing scheduling, lead capture, document intake
A booking assistant for hair salons and beauty studios.
  • Channels: WhatsApp
  • Services: Google Calendar, CRM, Stripe
  • Use cases: Appointment booking, service menu, reminders, payments
A membership assistant for gyms and fitness centers.
  • Channels: WhatsApp
  • Services: Google Calendar, CRM, Stripe (recurring subscriptions)
  • Use cases: Class scheduling, membership management, recurring billing, check-ins
A guest services assistant for hotels and accommodation.
  • Channels: WhatsApp + Voice
  • Services: Google Calendar, Stripe
  • Use cases: Reservation inquiries, check-in/check-out assistance, concierge requests, payments
A client assistant for accounting and tax consultancies.
  • Channels: WhatsApp + Email
  • Services: Google Calendar, CRM
  • Use cases: Appointment booking, document requests, deadline reminders, client communication
An autonomous AI content production pipeline for YouTubers and media creators.
  • Channels: Discord or Telegram (production team)
  • Services: YouTube API, HeyGen (avatar video), Google Calendar
  • Use cases: Script generation, avatar video production, upload scheduling, analytics monitoring

​
Operations templates

A gateway security monitoring agent with automated audit and hardening.
  • Tools: config_manage security audit, config_manage doctor, security-ops TOON guide
  • Scheduled tasks: Periodic security audits, anomaly detection, audit log review
  • Use cases: Continuous security posture monitoring, auto-remediation of common issues, tamper-evident audit trail
A site analytics and search performance agent.
  • Bundled skills: gsc-analytics (Google Search Console), site-auditor
  • Use cases: Keyword ranking tracking, crawl error detection, GSC data analysis, site performance reports

​
Deploying a template

Say what you need in natural language: 
"I want an assistant for my dental clinic"
GenosOS runs the guided flow automatically:
1

Identify the template

GenosOS detects “dental clinic” and matches the dental-clinic template. If multiple templates could match, it asks one clarifying question.
2

Create the agent

A single config_manage agents create call applies the full template: agent name, SOUL.md purpose injection, tool profile, allowed/denied tools, A2A wiring, and bundled skills installation.
3

Connect channels

If WhatsApp is not yet connected, GenosOS offers to connect it now. A QR overlay appears — scan it and it’s done. Voice (inbound calls) is activated with an auto-greeting.
4

Connect services

For calendar, CRM, and payment services, GenosOS walks through OAuth or API key setup. Credentials are stored in the encrypted vault automatically.
5

Security hardening

The agent’s security config is hardened automatically: shell tools disabled on messaging channels, DM policy set, vault auto-lock enabled.
6

Summary

GenosOS confirms what was configured: channels, services, tool profile, and any scheduled tasks. The agent is ready to receive messages.

​
Dental clinic example in full

From the architecture documentation — what happens when you say “I want an assistant for my dental clinic”: 
You:  "I want an assistant for my dental clinic"

GenosOS:  "Perfect. I need to know 3 things:
           1. What's your clinic called?
           2. How do your patients reach you? (WhatsApp, phone...)
           3. What should the assistant do? (answer questions, schedule
              appointments, both...)"

You:  "Clínica Dental Pozzi. WhatsApp and phone.
       Schedule appointments and answer questions about services."

GenosOS:  "Got it. Here's what I'll do:
           ● Create an agent called 'Clínica Dental Pozzi Assistant'
           ● Connect WhatsApp (I'll ask you to scan a QR code)
           ● Activate incoming calls
           ● Only you can manage it, for security
           Shall we start?"

You:  "Go ahead"

GenosOS: [creates agent → shows WhatsApp QR → activates voice inbound
          → hardens security config → seeds agent workspace]

          "WhatsApp connected. Calls activated.
           Do you have info about your services and hours?
           You can tell me here or send a document."
The user never saw dmPolicy, config_manage, blueprint, or inboundPolicy. All technical complexity ran behind the conversation.

​
After creation

Once your agent is running, you can extend it at any time: 
"Add Telegram to the dental clinic agent"
"Connect HubSpot to the dental clinic agent"
"Schedule a weekly appointment reminder at 9 AM on Mondays"
All changes happen conversationally — no config files to edit, no restarts required.
Channels are gateway-level infrastructure. If WhatsApp is already connected for your main agent, the new specialist agent can use it immediately — no reconnection needed.