Your customer context.
A clear data boundary.
Understand where customer knowledge lives and how it is used when you ask AI to work with it.
Readable customer memory
Customer facts live in local Markdown workspace files. Customer and business views are read-only derivatives of that memory. They do not become a separate authority for the relationship.
AI processing
Messages, authorized workspace excerpts and tool results can be sent to the selected AI provider. Codex uses OpenAI; a configured Claude engine uses Anthropic. The information used depends on the request, loaded context and permissions.
Local files do not mean fully offline inference, encryption or a security certification. Review the selected provider, account terms, workspace permissions and setup for your business.
Sources and changes
Read the supporting wording and review changes before relying on an answer. AI can misunderstand a note or produce an incomplete result. Source availability depends on how the information was captured and retained.
The website is separate
This website does not open your workspace, receive customer uploads or run a live AI conversation. The guided tour uses sample data. Website hosting and email enquiries have a separate boundary, described in Website privacy.
Lasting customer memory. Stronger relationships. Clearer next steps.
See PulseAI in your
customer workflow.
Bring a customer workflow you want to improve. See how PulseAI helps you retain what matters, prepare your next conversation and spot where to follow up.
Request a demo