SupportBuild with Ask360
Choose the fastest bulk importer for clean files or Ask360 for a validated, reviewed catalogue change.
How this fits into Lead360Explore the white label platformConnect client commerce, services, checkout, payments, and agency delivery.- 01
How Lead360 helps
- 02
Fastest path: Catalogue Import
- 03
Use Ask360 when the file needs review
- 04
Other catalogue work
How Lead360 helps
Build with Ask360 helps staff turn a commerce goal into a reviewable proposal for catalogue, service, membership, reward, or promotion setup. It can organize required fields and dependencies, while live creation and publication stay subject to the product workflow and user approval.
When to use this area
Use Build with Ask360 when the desired offer is clear but the team needs help preparing a complete, consistent configuration before creating live records.
Before you begin
- Describe the customer offer, price, audience, availability, and intended destination.
- Provide only approved business information and no credentials or payment data.
- Identify which records may be created or updated after review.
Fastest path: Catalogue Import
- For a clean bulk CSV or a Shopify or GoHighLevel export, open Catalogue Import in a new browser page.
- Upload the file, map source columns to Lead360 fields, verify every row, then import.
- This manual mapper is the recommended fast path for standard bulk imports and never needs store credentials.
Use Ask360 when the file needs review
- Attach exactly one compatible catalogue CSV of up to 500 rows.
- Attaching only stages the file. Review the request in the composer and press Send.
- Ask360 reports missing or invalid fields and duplicate risks, confirms matching by SKU or title, and shows an Accept or Decline review card. No catalogue item changes before Accept.
Other catalogue work
Ask360 can also list existing catalogue items or prepare one reviewed product, service, or package. Include exact type, name, price, currency, SKU, image, duration or inventory details as applicable.
Confirm the result
A completed Build with Ask360 workflow should be visible in the product area that owns the final record. Use these checks before relying on the result or moving to the next customer-facing step.
- Compare the proposal with source business requirements.
- Review every item, rule, date, amount, and dependency.
- After approved creation, test the live customer journey and payment behavior.
Troubleshooting
The proposal is incomplete
Add missing audience, pricing, dates, inventory, booking, membership, reward, or destination requirements before accepting any step.
The proposed record already exists
Search the live catalogue and related areas, then update or reuse the correct record instead of creating a duplicate.
Frequently asked questions
What should I confirm before using Build with Ask360?
Describe the customer offer, price, audience, availability, and intended destination. Provide only approved business information and no credentials or payment data. Identify which records may be created or updated after review. Start with a small, reviewable change whenever the workflow can affect customers, money, published content, or shared records.
How does Lead360 help with Build with Ask360?
Build with Ask360 helps staff turn a commerce goal into a reviewable proposal for catalogue, service, membership, reward, or promotion setup. It can organize required fields and dependencies, while live creation and publication stay subject to the product workflow and user approval.
Continue with Lead360
Use this workflow in Lead360
Put this guide into practice with a 14-day free trial of Lead360 Pro early access, or continue learning through the related collection.