Agents that remember and keep records.
Without a database to run.
Conversations pick up where they left off. Agents look up and update bookings or repairs and keep the files they produce. Every environment comes with its own storage, with nothing to set up.
From group bookings to supplier invoices.
A travel desk, a hotel and a property office let agents look up, write and file their own data. Staff see the same records in their own apps.
An event planner asks for 40 rooms near the congress center. The agent finds the closest hotels with free rooms and drafts a proposal for the travel desk to check.
Guests ask the hotel chat for pillows or a late checkout. The agent saves each request, and housekeeping marks it done on their board.
Once a month, an agent downloads supplier invoices and files them per building. The property office opens them in its own app, with amount and status.
Conversations continue the next day.
A tenant reports a repair in the evening and picks a slot the next morning. The agent still knows the flat, the repair and the slots it offered, because connic keeps each conversation's history between runs.
See every record your agents keep.
Agents write repairs, bookings and requests into their environment's database. Your team browses, filters and corrects them in the dashboard, with no database server to run.
- Search by value and distance
- Filter by exact values, ranges or distance from a place, or describe the filter in plain words.
- Start with the records you have
- Import a file of up to 25 MB into an empty collection, such as the buildings and technicians an agent should know.
- Files next to the records
- Agents save reports and downloads into folders. The dashboard shows them, and each run links to the files it wrote.
Decide in code what each agent may touch.
repairs-assistant keeps every text conversation, works with three collections and finds the closest technician with $near. The limits in its YAML apply on every run, also to your own tools.
- session
- One history per text conversation, keyed by
conversation_id.ttlends it after 14 days without a message. - concurrency
- Runs for the same conversation wait for each other, so two quick messages don't collide.
- database
- Limits the agent to
repairs,techniciansandbuildings, andprevent_deleteblocksdb_delete.
version: "1.0"
name: repairs-assistant
description: Logs tenants' repair requests and books a technician
model: connic/gpt-5.6-terra
system_prompt: |
Log repair requests from tenants and offer the
closest technician's free slots. Use what the
tenant already told you in this conversation.
tools:
- repairs.nearest_technicians
- db_insert
- db_update
session:
key: input.conversation_id
ttl: 1209600
concurrency:
key: conversation_id
on_conflict: queue
database:
collections: [repairs, technicians, buildings]
prevent_delete: truefrom connic.tools import db_find
async def nearest_technicians(building: str, trade: str) -> list:
"""Find the three closest technicians for a trade, within 15 km.
Args:
building: Building code, e.g. LIN-12
trade: heating, plumbing or electrical
"""
found = await db_find("buildings", filter={"code": building})
site = found["documents"][0]["location"]
result = await db_find(
"technicians",
filter={
"trade": trade,
"location": {"$near": {**site, "maxDistance": 15000}},
},
limit=3,
)
# Nearest first, each with _distance in meters
return result["documents"]