Agent Studio
Design, test, and
govern every workflow.
Design, test, and
govern every workflow.
Design, test, and
govern every workflow.
Agent Studio gives teams full control over how AI agents operate. Deterministic logic where regulation demands certainty. Intelligent flexibility where adaptation improves outcomes.
Agent Studio gives teams full control over how AI agents operate. Deterministic logic where regulation demands certainty. Intelligent flexibility where adaptation improves outcomes.
Specialty Drug Onboarding
Test
Publish
Caret
R
Procedures
New Patient Intake
Verify Patient Identity
Check Insurance Eligibility
Coverage Confirmed?
Submit Prior Authorization
Enrollment
Financial Assistance Review
Benefit Investigation
Prior Authorization
Financial Assistance Review
Document
Flow
Ryan
New Patient Intake
1.
Confirm the patient’s full name and date of birth. If the information does not match the record on file, do not proceed. Inform the patient that you are unable to verify their identity and escalate to a human specialist.
2.
Collect the patient's insurance provider, member ID, and group number. Run an eligibility check against the patient's current coverage. Document the outcome and note any gaps or limitations in coverage.
If
patient_coverage
is confirmed
A.
Execute Prior Authorization
End New Patient Intake
If
patient_coverage
is not confirmed
A.
Execute Financial Assistance Review
End New Patient Intake
From design to production.
From design to production.
Agent Studio gives teams the tools to define, validate, and govern agent workflows across every stage of deployment.
If Condition 1
Condition 1 say step Condo
AI Task
3214329382
Continue
to
Section 1
On Failure
Execute Procedure
Condition 1 say step Condo
AI Task
End
to
Procedure 2
AI Task Step
Nina
Agent Playbooks
Define how agents handle specific workflows from start to finish, built on your existing operating procedures. Every decision, data source, and outcome stays within the boundaries your team sets.
Define how agents handle specific workflows from start to finish, built on your existing operating procedures. Every decision, data source, and outcome stays within the boundaries your team sets.
Blueprints
Emma
Start from scratch
Missing Information Collection
Patient Intake
Appointment Scheduling
Benefits Verification
Program Enrollment
Validated Blueprints
Pre-built workflow templates for common pharma use cases across access and support. Teams can start from validated patterns and customize for specific brands, programs, or operational models.
Pre-built workflow templates for common pharma use cases across access and support. Teams can start from validated patterns and customize for specific brands, programs, or operational models.
Introduction
1.
Say "Hi, is this a good time to talk?"
Display name
@value
Expression
2.
Once the patient confirms availability and privacy, deliver: "Great, thank you. I am calling because we have your enrollment on file but need just a few additional details to get it completed and move things forward. This should only take a few minutes." Advance to the next step.
Dynamic Data and Tools
Agents connect to external systems and knowledge sources in real time, pulling the information each workflow requires. Every data retrieval and decision is traced for full auditability.
Agents connect to external systems and knowledge sources in real time, pulling the information each workflow requires. Every data retrieval and decision is traced for full auditability.
Testing, Evaluation, and Governance
Workflows are validated in staging environments before reaching production. In production, agent behavior, performance, and outcomes are continuously tracked. Issues surface before they become systemic.
Workflows are validated in staging environments before reaching production. In production, agent behavior, performance, and outcomes are continuously tracked. Issues surface before they become systemic.
and
and
Flow
Flow
Build agent workflows the way your team thinks best. The Document Editor uses natural language prompting for teams that design in prose. The Flow Editor uses visual logic for teams that design in structure. Both produce the same governed, production-ready output. Switch between them at any point, from first draft to deployment.
Patient Playbook
Test
Publish
Caret
E
Procedures
Introduction
Introduce yourself as Dez
Handle Explanation of Balance…
Handle Setting up a Payment…
Wants a different payment plan
Introduction
1.
Initiate the call with: “Hello, may I please speak with {{patientFirstName}}?” Wait for the caller's response. If the patient is available, continue: “Hi {{patientFirstName}}, this is an automated assistant calling on behalf of [programName] regarding your enrollment for {{medicationName}}. This call may be recorded for quality purposes. Do you have a few minutes to speak privately?”
If
patient
is unavailable
A.
Say, "No problem. We will try again at a better time. Thank you!" Set the callOutcome attribute to 'patientUnavailable' and schedule a follow-up attempt.
End Introduction
If
patient
is available but not private
A.
Say, "I understand. Since we will be discussing personal health information, I want to make sure you are in a comfortable setting. Is there a better time I can call you back?" Capture the preferred callback time and set the callOutcome attribute to 'callbackRequested'.
End Introduction
2.
Once the patient confirms availability and privacy, deliver: "Great, thank you. I am calling because we have your enrollment on file but need just a few additional details to get it completed and move things forward. This should only take a few minutes." Advance to the next step.
Verify Patient Identity
1.
Say, "Before we get started, I need to confirm a couple of details for security purposes." Use the patient record to verify identity using two of the following data points already on file. Ask: "Can you please confirm your date of birth?" Wait for the response and validate against patientDOB. Then ask: "And can you confirm the zip code on file for your address?" Wait for the response and validate against patientZip.
If
identityVerification
failed
A.
Say, “I am sorry, but I was not able to verify your identity with the information provided. For your security, I am unable to proceed. Please contact us directly at {{programPhoneNumber}} and a team member will be happy to assist you”
B.
Set callOutcome to identityVerificationFailed
End Verify Patient Identity
If
patient
is available but not private
A.
Say, "I understand. Since we will be discussing personal health information, I want to make sure you are in a comfortable setting. Is there a better time I can call you back?" Capture the preferred callback time and set the callOutcome attribute to 'callbackRequested'.
End Introduction
2.
Once both data points are confirmed, say: "Perfect, thank you for confirming that. Let me walk through the items we still need." Advance to the next step.
If Condition 1
Condition 1 say step Condo
AI Task
3214329382
Continue
to
Section 1
On Failure
Execute Procedure
Condition 1 say step Condo
AI Task
End
to
Procedure 2
AI Task Step
Document
Flow
Steph
Introduction
1.
Initiate the call with: “Hello, may I please speak with {{patientFirstName}}?” Wait for the caller's response. If the patient is available, continue: “Hi {{patientFirstName}}, this is an automated assistant calling on behalf of [programName] regarding your enrollment for {{medicationName}}. This call may be recorded for quality purposes. Do you have a few minutes to speak privately?”
If
patient
is unavailable
A.
Say, "No problem. We will try again at a better time. Thank you!" Set the callOutcome attribute to 'patientUnavailable' and schedule a follow-up attempt.
End Introduction
If
patient
is available but not private
A.
Say, "I understand. Since we will be discussing personal health information, I want to make sure you are in a comfortable setting. Is there a better time I can call you back?" Capture the preferred callback time and set the callOutcome attribute to 'callbackRequested'.
End Introduction
2.
Once the patient confirms availability and privacy, deliver: "Great, thank you. I am calling because we have your enrollment on file but need just a few additional details to get it completed and move things forward. This should only take a few minutes." Advance to the next step.
Verify Patient Identity
1.
Say, "Before we get started, I need to confirm a couple of details for security purposes." Use the patient record to verify identity using two of the following data points already on file. Ask: "Can you please confirm your date of birth?" Wait for the response and validate against patientDOB. Then ask: "And can you confirm the zip code on file for your address?" Wait for the response and validate against patientZip.
If
identityVerification
failed
A.
Say, “I am sorry, but I was not able to verify your identity with the information provided. For your security, I am unable to proceed. Please contact us directly at {{programPhoneNumber}} and a team member will be happy to assist you”
B.
Set callOutcome to identityVerificationFailed
End Verify Patient Identity
If
patient
is available but not private
A.
Say, "I understand. Since we will be discussing personal health information, I want to make sure you are in a comfortable setting. Is there a better time I can call you back?" Capture the preferred callback time and set the callOutcome attribute to 'callbackRequested'.
End Introduction
2.
Once both data points are confirmed, say: "Perfect, thank you for confirming that. Let me walk through the items we still need." Advance to the next step.
If Condition 1
Condition 1 say step Condo
AI Task
3214329382
Continue
to
Section 1
On Failure
Execute Procedure
Condition 1 say step Condo
AI Task
End
to
Procedure 2
AI Task Step
Document
Flow
Steph
Introduction
1.
Initiate the call with: “Hello, may I please speak with {{patientFirstName}}?” Wait for the caller's response. If the patient is available, continue: “Hi {{patientFirstName}}, this is an automated assistant calling on behalf of [programName] regarding your enrollment for {{medicationName}}. This call may be recorded for quality purposes. Do you have a few minutes to speak privately?”
If
patient
is unavailable
A.
Say, "No problem. We will try again at a better time. Thank you!" Set the callOutcome attribute to 'patientUnavailable' and schedule a follow-up attempt.
End Introduction
If
patient
is available but not private
A.
Say, "I understand. Since we will be discussing personal health information, I want to make sure you are in a comfortable setting. Is there a better time I can call you back?" Capture the preferred callback time and set the callOutcome attribute to 'callbackRequested'.
End Introduction
2.
Once the patient confirms availability and privacy, deliver: "Great, thank you. I am calling because we have your enrollment on file but need just a few additional details to get it completed and move things forward. This should only take a few minutes." Advance to the next step.
Verify Patient Identity
1.
Say, "Before we get started, I need to confirm a couple of details for security purposes." Use the patient record to verify identity using two of the following data points already on file. Ask: "Can you please confirm your date of birth?" Wait for the response and validate against patientDOB. Then ask: "And can you confirm the zip code on file for your address?" Wait for the response and validate against patientZip.
If
identityVerification
failed
A.
Say, “I am sorry, but I was not able to verify your identity with the information provided. For your security, I am unable to proceed. Please contact us directly at {{programPhoneNumber}} and a team member will be happy to assist you”
B.
Set callOutcome to identityVerificationFailed
End Verify Patient Identity
If
patient
is available but not private
A.
Say, "I understand. Since we will be discussing personal health information, I want to make sure you are in a comfortable setting. Is there a better time I can call you back?" Capture the preferred callback time and set the callOutcome attribute to 'callbackRequested'.
End Introduction
2.
Once both data points are confirmed, say: "Perfect, thank you for confirming that. Let me walk through the items we still need." Advance to the next step.
If Condition 1
Condition 1 say step Condo
AI Task
3214329382
Continue
to
Section 1
On Failure
Execute Procedure
Condition 1 say step Condo
AI Task
End
to
Procedure 2
AI Task Step
Document
Flow
Steph
Introduction
1.
Initiate the call with: “Hello, may I please speak with {{patientFirstName}}?” Wait for the caller's response. If the patient is available, continue: “Hi {{patientFirstName}}, this is an automated assistant calling on behalf of [programName] regarding your enrollment for {{medicationName}}. This call may be recorded for quality purposes. Do you have a few minutes to speak privately?”
If
patient
is unavailable
A.
Say, "No problem. We will try again at a better time. Thank you!" Set the callOutcome attribute to 'patientUnavailable' and schedule a follow-up attempt.
End Introduction
If
patient
is available but not private
A.
Say, "I understand. Since we will be discussing personal health information, I want to make sure you are in a comfortable setting. Is there a better time I can call you back?" Capture the preferred callback time and set the callOutcome attribute to 'callbackRequested'.
End Introduction
2.
Once the patient confirms availability and privacy, deliver: "Great, thank you. I am calling because we have your enrollment on file but need just a few additional details to get it completed and move things forward. This should only take a few minutes." Advance to the next step.
Verify Patient Identity
1.
Say, "Before we get started, I need to confirm a couple of details for security purposes." Use the patient record to verify identity using two of the following data points already on file. Ask: "Can you please confirm your date of birth?" Wait for the response and validate against patientDOB. Then ask: "And can you confirm the zip code on file for your address?" Wait for the response and validate against patientZip.
If
identityVerification
failed
A.
Say, “I am sorry, but I was not able to verify your identity with the information provided. For your security, I am unable to proceed. Please contact us directly at {{programPhoneNumber}} and a team member will be happy to assist you”
B.
Set callOutcome to identityVerificationFailed
End Verify Patient Identity
If
patient
is available but not private
A.
Say, "I understand. Since we will be discussing personal health information, I want to make sure you are in a comfortable setting. Is there a better time I can call you back?" Capture the preferred callback time and set the callOutcome attribute to 'callbackRequested'.
End Introduction
2.
Once both data points are confirmed, say: "Perfect, thank you for confirming that. Let me walk through the items we still need." Advance to the next step.
If Condition 1
Condition 1 say step Condo
AI Task
3214329382
Continue
to
Section 1
On Failure
Execute Procedure
Condition 1 say step Condo
AI Task
End
to
Procedure 2
AI Task Step
Document
Flow
Steph
Introduction
1.
Initiate the call with: “Hello, may I please speak with {{patientFirstName}}?” Wait for the caller's response. If the patient is available, continue: “Hi {{patientFirstName}}, this is an automated assistant calling on behalf of [programName] regarding your enrollment for {{medicationName}}. This call may be recorded for quality purposes. Do you have a few minutes to speak privately?”
If
patient
is unavailable
A.
Say, "No problem. We will try again at a better time. Thank you!" Set the callOutcome attribute to 'patientUnavailable' and schedule a follow-up attempt.
End Introduction
If
patient
is available but not private
A.
Say, "I understand. Since we will be discussing personal health information, I want to make sure you are in a comfortable setting. Is there a better time I can call you back?" Capture the preferred callback time and set the callOutcome attribute to 'callbackRequested'.
End Introduction
2.
Once the patient confirms availability and privacy, deliver: "Great, thank you. I am calling because we have your enrollment on file but need just a few additional details to get it completed and move things forward. This should only take a few minutes." Advance to the next step.
Verify Patient Identity
1.
Say, "Before we get started, I need to confirm a couple of details for security purposes." Use the patient record to verify identity using two of the following data points already on file. Ask: "Can you please confirm your date of birth?" Wait for the response and validate against patientDOB. Then ask: "And can you confirm the zip code on file for your address?" Wait for the response and validate against patientZip.
If
identityVerification
failed
A.
Say, “I am sorry, but I was not able to verify your identity with the information provided. For your security, I am unable to proceed. Please contact us directly at {{programPhoneNumber}} and a team member will be happy to assist you”
B.
Set callOutcome to identityVerificationFailed
End Verify Patient Identity
If
patient
is available but not private
A.
Say, "I understand. Since we will be discussing personal health information, I want to make sure you are in a comfortable setting. Is there a better time I can call you back?" Capture the preferred callback time and set the callOutcome attribute to 'callbackRequested'.
End Introduction
2.
Once both data points are confirmed, say: "Perfect, thank you for confirming that. Let me walk through the items we still need." Advance to the next step.
If Condition 1
Condition 1 say step Condo
AI Task
3214329382
Continue
to
Section 1
On Failure
Execute Procedure
Condition 1 say step Condo
AI Task
End
to
Procedure 2
AI Task Step
Document
Flow
Steph
Meet
Caret
Meet
Caret
Your always-on AI assistant
Your always-on AI assistant
Caret works alongside your team
Caret works alongside your team
It drafts playbook logic from plain-language descriptions, transforms uploaded SOPs into optimized playbooks, surfaces best practices, and executes tasks within Agent Studio on your team's behalf. The result is faster iteration from first draft to production-ready workflow.
It drafts playbook logic from plain-language descriptions, transforms uploaded SOPs into optimized playbooks, surfaces best practices, and executes tasks within Agent Studio on your team's behalf. The result is faster iteration from first draft to production-ready workflow.
Start focused.
Prove impact.
Confidently scale.
Start focused.
Prove impact.
Confidently scale.
Most teams begin with a use case or micro journey. We will talk through your operating model, where execution breaks down, and whether Elegant Machine is the right fit.
HIPAA Compliant
SOC2 Type II
© Elegant Machine 2026
HIPAA Compliant
SOC2 Type II
© Elegant Machine 2026
HIPAA Compliant
SOC2 Type II
© Elegant Machine 2026
HIPAA Compliant
SOC2 Type II
© Elegant Machine 2026
HIPAA Compliant
SOC2 Type II
© Elegant Machine 2026