Ask AI to combine a customer record with session records for a support brief or update the profile fields you provide.
Copy a prompt into your agent with the oo Skill installed. Add your page links and source notes before running it.
Look up a customer and organize their matching session records.
/oo Atlas.so: Look up Atlas customer [email] and list sessions for that email from [start time] to [end time]. Summarize the recorded pages and session details, noting fields not present.
Confirm a customer and apply exact profile corrections.
/oo Atlas.so: Find Atlas customer [email], read their record, and update only these fields [names and values]. Report the customer ID and changed fields.
Set up oo CLI and the oo Skill in your agent.
Install OOMOL →Connect your Atlas.so API key.
Connect Atlas.so →Use /oo with the pages to read, the changes to make, and where to save the result.
Connection Guide →Choose Your Agent
Atlas.so stores customer, account, and session records. The connection can read these records and maintain customer or account profiles.
Read account and customer records and create or update supplied profile information.
List session records with customer, page, and date filters.
List Atlas accounts visible to the current API key.
Leina 
Wanta 
atlas_so.list_accounts Retrieve a single Atlas account by ID.
atlas_so.get_account Create or update an Atlas account using the account upsert endpoint.
atlas_so.upsert_account List Atlas customers visible to the current API key.
atlas_so.list_customers Retrieve a single Atlas customer by ID.
atlas_so.get_customer Retrieve a single Atlas customer by ID, email, phone number, or user ID.
atlas_so.lookup_customer Create an Atlas customer.
atlas_so.create_customer Update an Atlas customer by ID.
atlas_so.update_customer Create or update an Atlas customer using the customer upsert endpoint.
atlas_so.upsert_customer List Atlas session recordings with optional customer and date filters.
atlas_so.list_sessions No matching tools.
Lookup accepts a customer ID, email, phone number, or user ID. Use a stable identifier when several customers have similar names.
It summarizes the session fields provided by the listing. It does not automatically watch a recording or infer actions absent from those fields.
Yes. Specify the customer ID and exact profile fields to change. The assistant can read the record before updating it.
Manage which optional storage OOMOL can use. You can change these choices from the footer at any time.