Talk to Juulio sales

Key facts

• Primary contact mode: Sales inquiry
• Preferred contact options: Email, Phone, Text message
• Submission CTA: Send to sales
• Required contact identity: firstName, lastName, email, phone
• Quick starts supported: Conversation starters

Talk to Juulio sales

Share your goals, current workflow, or rollout questions and a product specialist will follow up.

• Contact details: shop identity and operator context
• Interest areas: pricing, implementation, integrations, migration, and reporting
• How can we help?: describe rollout or workflow questions before follow-up

Required contact fields

A confirmed contact-sales submit must include the minimum fields below.

• firstName
• lastName
• email
• phone

Confirmation and anti-abuse expectations

Agent submits require operator confirmation, auth, and idempotency.

• submit_contact_sales requires operatorConfirmation=true
• submit_contact_sales requires x-idempotency-key
• duplicate idempotency keys must not create duplicate contact-sales submissions

Allowed actions

Markdown mirror

# Talk to Juulio sales

Share your goals, current workflow, or rollout questions and a product specialist will follow up.

Human page: https://juulio.com/contact-sales
Path: /contact-sales
Locale: en-US
Schema version: 2026-04-06.agent-surface.v1
Content version: 2026-04-06

## Key facts
- Primary contact mode: Sales inquiry
- Preferred contact options: Email, Phone, Text message
- Submission CTA: Send to sales
- Required contact identity: firstName, lastName, email, phone
- Quick starts supported: Conversation starters

## Talk to Juulio sales
Share your goals, current workflow, or rollout questions and a product specialist will follow up.
- Contact details: shop identity and operator context
- Interest areas: pricing, implementation, integrations, migration, and reporting
- How can we help?: describe rollout or workflow questions before follow-up

## Required contact fields
A confirmed contact-sales submit must include the minimum fields below.
- firstName
- lastName
- email
- phone

## Confirmation and anti-abuse expectations
Agent submits require operator confirmation, auth, and idempotency.
- submit_contact_sales requires operatorConfirmation=true
- submit_contact_sales requires x-idempotency-key
- duplicate idempotency keys must not create duplicate contact-sales submissions

## Allowed actions
- `get_contact_sales_context` (POST /api/public/agent/contact-sales/context) - Return current public contact-sales context and quick starts. Required fields: none.
- `draft_contact_sales` (POST /api/public/agent/contact-sales/draft) - Normalize contact-sales fields and identify missing requirements before submit. Required fields: locale.
- `submit_contact_sales` (POST /api/public/agent/contact-sales/submit) - Create a single confirmed contact-sales submission on behalf of an operator. Required fields: firstName, lastName, email, phone, operatorConfirmation. Requires explicit operator confirmation.