ROCKETLY HELP CENTER
Evaluate the product with the right scope.
This page gives general answers for teams evaluating Rocketly for customer conversations, sales follow-up, and controlled automation. Availability can vary by role, plan, organization settings, and connected-provider configuration.
Start with a small, reviewable flow.
Apply your own policies to critical decisions, permissions, and customer data. Validating a setup with a small sample is safer than enabling a broad workflow at once.
18 REVIEWED ANSWERS
Because plan, role, and provider conditions can vary, verify critical steps in your own environment.
Getting started and teams
Core questions for matching a new workspace to the way your team actually works.
What is Rocketly for?
Rocketly is a CRM that helps organize customer conversations, records, ownership, and follow-up steps in one shared workspace. Teams configure their process around their own roles and working rules.
Where should I start setup?
Start with the channels you genuinely use, record owners, and sales or service stages. Review access, data mapping, and follow-up with a small test group before expanding the scope.
Does every team member see the same features?
No. Visible fields and actions can vary by role, organization settings, and active product scope. An administrator should define access decisions and review them regularly.
Customer records and sales follow-up
Keep context in accountable records rather than personal notes.
What should I do before moving existing customer data?
Validate field mapping, duplicate handling, and consent with a small representative sample first. Incomplete or inaccurate source data remains incomplete or inaccurate after import, so name a data owner before moving it.
Why should an opportunity or request have an owner?
Ownership makes responsibility for the customer’s next step visible. A record becomes easier to hand over when it carries its context, accountable owner, and planned follow-up together.
Do reports guarantee a sales outcome?
No. Reports help inspect recorded data and spot exceptions. Data quality, period, context, and the team’s judgment should be considered together before a decision.
Conversations and follow-up
Protect context and the next action in customer communication.
How should I evaluate multiple channels?
Channel connections depend on provider permissions and your organization configuration. Confirm the channels you need, then agree on ownership, working hours, and customer-response expectations as a team.
What matters when handing a conversation to a teammate?
Customer context, an open follow-up, the responsible person, and any necessary internal note should be readable in the same record. Treat handoff as a reviewable process, not only an assignment action.
Is it safe to automate recurring follow-up?
It can be for a tested, low-risk rule. Define the exception path and review the result first; actions involving consent, customer preference, or financial consequences may need additional control.
AI and workflows
Use assistance while preserving human responsibility.
What role can AI play?
AI can support work such as summarizing, routing, or preparing a draft using information and rules your organization authorizes. The user remains responsible for accuracy, suitability, and any action taken from the output.
What should I check before enabling a workflow?
Test the trigger, conditions, exception path, owner, and rollback approach in a small scope. Also test what happens for different record types and permission states.
Does automation guarantee revenue or an outcome?
No. Automation helps organize repeatable parts of a process; customer response, sales outcomes, and operational impact depend on many external factors.
Integrations and data
Keep permissions, data quality, and connected-system scope explicit.
Does an integration work the same way for every organization?
No. Availability can depend on the provider account, plan, permissions, and organization settings. Confirm provider scope, permissions, and the error path before relying on a live data flow.
What boundaries matter for an API or webhook?
Protect credentials, send only necessary data, and design error and retry behavior explicitly. Ownership, auditability, and access limits should be clear on both sides of an integration.
Does the platform guarantee historical data accuracy?
No. The data owner remains responsible for accuracy, consent, and freshness. Regular sample review and a clear correction process support a more reliable operating rhythm.
Security and account
Basic operating principles for account access and customer data.
How can I keep access safer?
Give each user only the access needed for their work, avoid shared accounts, and review access regularly. Where available, evaluate strong sign-in methods and additional verification.
What is the right approach to sensitive customer data?
Collect only what is needed, limit access by role and purpose, set retention expectations, and follow applicable law and your organization policy. Rocketly is not legal advice or a replacement for those responsibilities.
When should I contact support?
For an access issue, data-mapping question, provider connection, or unexpected behavior, collect the relevant record and error context first. Your team can then seek safer, faster help through the support channel.