SupportAsk360 workspace overview
Use the tenant-scoped Ask360 workspace to investigate, draft, and coordinate approved work across Lead360.
How this fits into Lead360Explore Ask360See how Pieces, memory, channels, playbooks, learning, and kits work together.- 01
How Lead360 helps
- 02
Before you begin
- 03
Complete the workflow
- 04
Understand the key controls
How Lead360 helps
The Ask360 workspace brings current sub-account context, supported product tools, bots, channels, connectors, playbooks, governed memory, and plugins into one operational area. Ask360 can explain records and prepare work, while permissions and confirmation policies continue to control live effects.
When to use this workflow
Use the workspace when the task spans more than one Lead360 area or when staff need help understanding context before opening the feature that owns the final change.
Before you begin
Start with the exact sub-account and the smallest set of permissions, records, and resources required for the task.
- Confirm the current sub-account and signed-in role.
- State one concrete outcome and identify the relevant customer or business records.
- Decide whether the request is read-only, a draft, or a proposed live action.
Complete the workflow
Follow the steps in order and stop when a required resource, permission, review, or approval is missing.
- Open Ask360 from the current Lead360 sub-account.
- Describe the outcome, scope, time range, and records involved.
- Review cited source records and ask follow-up questions when context is incomplete.
- Inspect every proposed operation, target, and effect before approval.
- Confirm any approved change in the owning Lead360 feature.
Understand the key controls
Tenant scope
Ask360 uses the current sub-account context. It does not treat a user request as permission to cross into another tenant.
Human confirmation
Consequential operations can require explicit confirmation even when the user and bot have the underlying capability.
Product ownership
Ask360 can coordinate a task, but Contacts, Conversations, Payments, Automations, Sites, and other product areas remain the source of truth for their records.
Confirm the result
Do not rely on a success message alone. Confirm the saved state and any live effect in the product area that owns the final record.
- Check that source links belong to the intended sub-account.
- Compare drafts with live values before using them.
- Review the audit or run record for any approved operation.
Troubleshooting
Ask360 is missing needed context
Open the relevant product page, provide the exact record identifier, or attach reviewed memory rather than pasting sensitive data into chat.
Ask360 refuses an action
Check user permission, bot capability, effect policy, resource mapping, and confirmation requirements. A refusal may be the expected control.
Frequently asked questions
Can Ask360 make changes automatically?
Only supported operations with the required user authority, bot capability, tenant binding, and effect policy can reach a live change. Consequential actions can still require explicit confirmation.
Does Ask360 replace the Lead360 product pages?
No. Ask360 helps investigate, draft, and coordinate work. The product area that owns a record remains the authoritative place to verify the final state.
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.