Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.utari.ai/llms.txt

Use this file to discover all available pages before exploring further.

JeremyAI is your place to ask questions, work through business problems, review files and links, use JeremyAI skills, create or use workers when available, and talk to JeremyAI by voice when voice is enabled. The best way to start is with one real business problem, asset, offer, funnel, sales question, file, or link you already care about. JeremyAI works better when you give it context instead of asking a broad question with no details.

​
Watch the walkthrough

​
Sign in to JeremyAI

Go to jeremy.utari.ai and enter the email address that was invited to JeremyAI. JeremyAI will send a 6-digit sign-in code to that email address. Open the email, copy the code, and enter it on the sign-in screen. Once the code is accepted, you will land inside JeremyAI. If the sign-in email or code does not arrive, check spam or promotions first. If it still is not there, email hey@utari.ai with the email address you are trying to use.

​
What you will see inside JeremyAI

Inside JeremyAI, you will see:
  • New Chat: start a fresh conversation.
  • Chats: reopen past conversations.
  • New Voice Call: start a voice conversation with JeremyAI.
  • Workers: use available JeremyAI workers or create personal workers when enabled.
  • Triggers: create automations when trigger access is enabled.
  • Skills: browse what JeremyAI can do.
  • Profile/account menu: manage account-level options.
You do not need to open Skills before asking for help. The Skills area is useful for discovery, but you can ask naturally in chat and JeremyAI can choose the right skill when your request matches an available skill.

​
Start with a real business problem

JeremyAI works best when you bring it something real: an offer, funnel, ad, landing page, VSL, sales call issue, follow-up problem, file, or link. Instead of asking a broad question, give JeremyAI the situation and ask it to diagnose what matters most. Good first requests look like:
  • “Here is my offer and audience. Tell me what is unclear, what is weak, and what Jeremy would fix first.”
  • “Here is my funnel or landing page. Summarize what matters, identify the biggest conversion issue, and tell me the first improvement to make.”
  • “I want to build or improve a VSL for this offer. Ask me what you need before writing the outline.”
  • “I am stuck on this sales problem. Diagnose the likely bottleneck and tell me what to fix first.”

​
First prompt to try

Copy this into a new chat and fill in the brackets: I want JeremyAI to help me build or improve a VSL for a real offer.

My offer is: [describe the offer]
My audience is: [who buys it]
The problem they want solved is: [main pain or frustration]
The result I promise is: [main outcome]
My proof is: [case studies, results, testimonials, personal proof, or what proof is missing]
My current sales path is: [webinar, call funnel, ads, organic, email, landing page, etc.]
If I have an existing page, script, ad, funnel, or notes, I will paste or upload them here: [file/link/context]

First, summarize what you understand about the offer. Then tell me what is unclear, what Jeremy would fix first, and what missing questions you need answered. After that, build a simple VSL outline with the hook, problem, mechanism, proof, offer, and call to action.\ JeremyAI may ask clarifying questions before it writes the full script. That is normal when the request needs more detail.

​
Bring JeremyAI the real material

JeremyAI is most useful when it can work from the actual thing you want improved. Instead of describing a funnel from memory, paste the page. Instead of explaining a VSL in general terms, upload the script or notes. Instead of asking for generic strategy, give JeremyAI the offer, audience, current sales path, and what is not working. Useful material to share includes:
  • offer notes
  • landing pages
  • VSL scripts or outlines
  • ads or creative briefs
  • sales call notes
  • follow-up messages
  • customer objections
  • funnel screenshots or links
  • reports, scorecards, or performance numbers
When you share material, tell JeremyAI what decision you want help making. Examples:
  • “Review this landing page and tell me the biggest reason people may not book.”
  • “Use this VSL outline to identify what is unclear, what is weak, and what Jeremy would fix first.”
  • “Read these sales call notes and tell me the pattern behind the objections.”
  • “Look at these funnel numbers and diagnose the first bottleneck to fix.”
Note: If you share a document or link, make sure it can be viewed by anyone with the link. JeremyAI will not be able to read private, login-protected, blocked, or permission-restricted links. Keep the conversation in the same chat when the context should carry forward. Start a new chat when you switch to a different offer, project, or problem.

​
Use voice when talking is easier

Use New Voice Call when you want to talk through an idea out loud instead of typing. Voice Calls are useful for explaining context quickly, pressure-testing an idea, or thinking through a sales, offer, or funnel decision.

​
If something breaks

Email hey@utari.ai and include:
  • the account email you use for JeremyAI
  • what you tried
  • what happened
  • what you expected
  • any file, link, voice call, worker, or skill involved
  • a screenshot or short screen recording when possible