Support & Help Center

Every team has questions when it adopts a new way of working. Amarnex connects you with practical guidance and assisted support so you can understand the next step, explain the issue clearly, and keep your property operations moving.

Find help through the chat, email, and phone channels described in Amarnex, alongside guides and frequently asked questions. Whether you are preparing your first migration, reviewing a sales workflow, or investigating a platform issue, start with the support path that fits your need.

Explore Guides & FAQs

Product guidance

Use guides and FAQs to understand the journey behind the task. Begin with the module you are using, the record you are working on, and the outcome you want to achieve. If you need more context, contact the team with a concise description of your question.

Customer assistance

Speak with the team through the available chat, email, or phone route. Explain the business process involved and what you expected to happen. Clear context makes it easier to direct the question to the appropriate person without asking you to repeat the whole story.

Technical assistance

For a platform problem, describe what happened and the steps that led to it. Include the time, module, browser or device, and any visible error message. Use an approved support channel for necessary screenshots, with unrelated personal or confidential information removed.

Onboarding and migration

Discuss the records you want to bring into Amarnex and the way your teams work today. A shared understanding of data scope, responsibilities, and validation helps make the start more manageable.

Before onboarding discussions, identify a business owner who can explain the process and a data owner who can validate the source information. List the projects, teams, and workflows included in the first phase, then identify where information currently lives.

Agree the outcomes you want to review: the records that should be available, the users who need access, and the stages each team expects to follow. Keep questions about optional features, integrations, and custom work visible so they can be included in the implementation scope where appropriate.

These preparation steps are guidance for your team. The actual onboarding activities, training, schedule, and responsibilities depend on the services agreed with Amarnex.

Presentation v1.9 describes free migration assistance for new clients, covering leads, customers, users, units, projects, bookings, sales records, and related operational data from existing systems or Excel sheets. Discuss the current offer, source formats, data volume, and agreed scope before scheduling the work.

Prepare: Identify the source systems and the person authorized to share each dataset. Review duplicates, incomplete fields, inconsistent naming, and records that no longer belong in the migration.

Map: Explain how your existing project, unit, customer, and transaction references relate to one another. Agree how those records should be represented in Amarnex and which items need separate review.

Validate: Nominate people to check representative records and business relationships after the agreed transfer. Keep a list of questions and discrepancies for resolution before relying on migrated information operationally.

Protect: Use only the transfer method agreed with the team. Do not paste customer databases into an open enquiry form or send passwords, payment credentials, or identity documents unless a specific secure process requires and authorizes them.

Discuss Migration

Leads and customer records: Explain the source, assigned owner, or customer context you are trying to understand. Use a record reference instead of copying the customer’s full personal details into the first message.

Sales and contracts: Identify the current stage and the next expected action. If a business approval is required, involve the person authorized to make that decision; support does not replace your commercial or legal approval process.

Payments and collection: Describe the invoice or payment-status question and the affected record. Your finance team remains responsible for checking actual funds and approving financial actions.

Project and customer communication: Explain the update, channel, and intended recipient group. Confirm whether the question concerns configuration, content, or a third-party delivery service.

AI agents and connectors: State the agent or connection involved and the expected outcome. Integration scope, provider permissions, and configured workflows can affect behavior. Do not include API secrets or confidential customer conversations in an initial open enquiry.

A clear request should contain the organization or tenant reference, your role, the module, the task you were attempting, what you expected, what actually happened, the time and time zone, and whether the issue affects one record or a wider workflow.

If possible, describe reproducible steps and share the exact error text. Mention whether the issue prevents work or whether a temporary alternative is available. This helps the team understand business impact without inventing urgency classifications or response commitments.

Keep passwords, one-time codes, payment-card details, API keys, and unrelated personal data out of support messages. Support should use the agreed authorization process if access to tenant information is needed.

How can we contact support?

Amarnex describes chat, email, and phone support. Use the verified destinations provided in your onboarding information or the live website.

Are guides and FAQs available?

The presentation includes self-help guides and FAQs. Start with the published resources relevant to your task; ask the team if you cannot find the right topic.

Can we migrate from another system or Excel?

Yes, migration assistance from existing systems and Excel is described in v1.9. Confirm the current offer and agree the record types, formats, scope, and validation responsibilities.

Does the migration offer include every file or custom integration?

Do not assume universal coverage. Share your requirements so the team can confirm included work and identify anything requiring a separate scope.

Who should approve changes to our workflow or access?

Your authorized tenant administrator or business owner should confirm changes within their responsibility. Support assistance does not remove your internal approval requirements.

What if a connector is not behaving as expected?

Identify the provider, affected record, expected direction of data flow, and relevant time. The team can then discuss the configured scope and whether the issue needs coordination with the provider.

Can support approve a contract or confirm that a customer has paid?

Business and legal approvals remain with the authorized parties. Your finance team should verify actual funds; a support conversation is not a payment confirmation or legal approval.

Where do we raise a data-access or privacy concern?

Use the verified privacy or support contact and provide a concise description without unnecessary personal data. State whether you are the tenant’s authorized representative or an individual asking about personal information.

Are there guaranteed response times or round-the-clock support?

Refer to the service terms agreed with Amarnex. This page does not establish a response-time guarantee, resolution deadline, or 24/7 service.

Bring your question, your current workflow, and the outcome you need. Contact Amarnex for product guidance, technical assistance, or help planning a clearer start.

Discuss Onboarding