CRM Customer Support for Small Businesses: How to Get Help Without Slowing Down Your Team

CRM customer support should help a small business solve problems without creating another complicated process.

When a contractor, office manager, or business owner needs assistance, they should not have to search through old emails, open several ticketing systems, or explain the entire company setup every time.

With DunaHub Support, users can contact the product team directly from the dashboard.

The conversation remains connected to the organization, which means authorized team members can review previous messages, see the replies, and continue the discussion from the same place.

Support can help with questions related to:

• account settings;
• billing;
• plan changes;
• organization ownership;
• platform features;
• integration setup;
• unexpected errors;
• feature requests;
• general product usage.

Organizations using a Growth Package also receive a dedicated Growth Manager channel for advertising, landing pages, lead-flow strategy, and campaign reviews.

Why does CRM support matter for small businesses?

Small companies often do not have a dedicated IT department.

The person asking for support may also be responsible for:

• answering leads;
• preparing estimates;
• managing employees;
• scheduling jobs;
• sending invoices;
• following up with customers;
• running advertising campaigns.

A technical issue can interrupt several parts of the operation.

For example, if WhatsApp stops connecting, the business may lose access to an important customer channel.

If an invoice does not sync with QuickBooks, the accounting workflow may become incomplete.

If an employee cannot access the organization, a customer may wait longer for a response.

Good support reduces the amount of time the team spends trying to diagnose problems alone.

Where can users find DunaHub Support?

The support channel is available inside the DunaHub dashboard.

To open it:

1. Sign in to the organization;
2. Open the dashboard sidebar;
3. Find Support below the Growth section;
4. Click the Support entry;
5. Write the question in the message box;
6. Press Enter to send.

Use Shift + Enter when you need to create a new line without sending the message.

If the DunaHub team has replied and the message has not been read, a notification badge appears beside the Support entry.

This helps the user notice that a response is available without repeatedly checking the page.

Is Support available on every plan?

Yes.

The general Support channel is available to organizations using the standard DunaHub plans.

These include:

• Free;
• Starter;
• Pro.

A business does not need to purchase the Pro plan simply to ask a product or account question.

The same general support channel can be used for topics such as:

• how to configure a feature;
• billing questions;
• plan upgrades or downgrades;
• integration problems;
• account ownership;
• unexpected system behavior.

The DunaHub plans and pricing determine feature limits, users, automations, and other platform capabilities, but general support remains available across the plans.

Is the support conversation private to one employee?

No.

The support conversation is saved at the organization level.

Authorized users in the same organization can read the previous messages and continue the conversation.

This is useful when:

• the person who opened the request is unavailable;
• another employee has more technical information;
• the owner needs to review a billing discussion;
• several people are affected by the same issue;
• a manager needs to confirm the solution.

For example:

1. An office administrator reports that customer emails are not appearing;
2. DunaHub Support asks for the email provider and settings;
3. The administrator leaves for the day;
4. The owner opens the same support conversation;
5. The owner provides the missing information;
6. The team continues without creating a duplicate request.

Because the conversation is shared, employees should avoid including information that unrelated users in the organization should not see.

What is the typical response time?

The typical response time for general Support is the same business day during U.S. business hours.

This should be treated as a normal expectation, not an absolute guarantee for every message.

Response time can depend on:

• time of submission;
• complexity;
• information provided;
• whether the issue requires investigation;
• whether the message arrives outside business hours;
• whether the problem affects one account or the entire platform.

Non-urgent messages sent outside business hours are normally handled on the next business day.

A clear initial message can reduce unnecessary back-and-forth and help the team investigate faster.

What should users send to Support?

Support can assist with issues related to the DunaHub account and platform.

Account questions

Examples include:

• How do I change the organization owner?
• Where can I update billing information?
• How do I upgrade to Pro?
• What happens if I cancel?
• How can I remove a former employee?
• Why does a user not see the organization?

How-to questions

Examples include:

• How do I create a pipeline stage?
• How do I publish an online booking page?
• How do I connect WhatsApp?
• How do I send a proposal?
• How do I import a CSV?
• How do I enable the live chat widget?

Before contacting Support, users can also review the DunaHub documentation for step-by-step guides.

Bug reports

A bug report is appropriate when a feature does not behave as documented.

Examples include:

• a button does not respond;
• a page fails to load;
• an invoice shows the wrong status;
• a conversation does not appear;
• an automation does not trigger;
• a user receives an unexpected error.

Screenshots are especially useful when the issue is visual or produces an error message.

Feature requests

Support can receive suggestions about improvements or additions.

A useful request explains:

• the problem;
• the current workaround;
• who experiences it;
• how often it happens;
• what outcome would help.

Instead of writing:

Add more features to jobs.

Write:

Our technicians need to attach completion photos to each job. We currently store them in a separate folder, which makes it difficult for the office to review the work.

The second request gives the product team more useful context.

Integration help

Support can assist with documented integrations such as:

• WhatsApp;
• Twilio;
• Stripe;
• QuickBooks.

The team may ask for:

• connection status;
• error message;
• account region;
• steps already completed;
• time the issue occurred;
• affected record.

What should a good support request include?

A useful request allows the support team to understand the situation without guessing.

Include the following information when relevant.

1. A clear subject or first sentence

Begin with a direct description.

Example:

New QuickBooks invoices stopped syncing this morning.

Avoid:

It is not working.

2. The affected feature

Name the relevant area.

Examples:

• Inbox;
• WhatsApp;
• QuickBooks;
• proposals;
• jobs;
• online booking;
• webchat;
• missed-call text-back;
• invoices;
• automations.

3. What you expected

Explain the intended outcome.

Example:

I expected the approved proposal to create a new scheduled job.

4. What happened instead

Describe the actual result.

Example:

The proposal shows Approved, but no job was created.

5. Steps to reproduce the issue

List the actions that caused the problem.

Example:

1. Opened the lead;
2. Created a proposal;
3. Sent the public link;
4. Approved it from another browser;
5. Returned to the lead;
6. No job appeared.

6. Time of occurrence

A timestamp helps the team review logs.

Include:

• date;
• approximate time;
• time zone.

7. Screenshot

Attach a screenshot when possible.

Make sure it shows:

• the relevant area;
• complete error message;
• status;
• important context.

Hide private customer information when it is not needed.

8. Browser or device

For display or login problems, mention:

• browser;
• operating system;
• desktop or mobile;
• whether private mode was tested.

9. Whether other users are affected

Explain whether the issue affects:

• one user;
• all users;
• one lead;
• all leads;
• one device;
• several devices.

This helps identify whether the issue is local or organization-wide.

Example of a strong support message

Hi, our QuickBooks invoices stopped syncing today, June 24, around 10:30 AM Eastern Time. The QuickBooks settings page still shows Connected. I created two invoices in DunaHub, but neither appeared in QuickBooks. Existing invoices are still visible. I attached a screenshot of the connection page and the error shown on one invoice. Could you check whether the token or sync is failing?

This message gives Support:

• the feature;
• the date;
• the time;
• the current status;
• the affected records;
• the expected result;
• a screenshot;
• a specific question.

Example of a weak support message

QuickBooks is broken. Please fix.

This does not explain:

• what failed;
• when it failed;
• whether the account is connected;
• whether one or all invoices are affected;
• whether an error appeared.

Support will need to ask several questions before investigating.

Should users open several messages for the same problem?

Normally, no.

Continue using the same organization support conversation when the subject is part of an existing issue.

Sending repeated versions of the same request can make it harder to follow:

• what was already tested;
• which employee replied;
• whether the issue changed;
• which answer is current.

A follow-up can say:

We tested the steps you suggested. The issue still happens, but only for invoices containing the “Emergency Service” item.

That adds useful new information without restarting the conversation.

What is the Growth Manager channel?

Organizations subscribed to a Growth Package receive an additional tab called Growth Manager.

The Support page then shows two distinct channels:

Support

Used for:

• product questions;
• account questions;
• billing;
• technical problems;
• integrations;
• feature guidance.

Growth Manager

Used for:

• Google Ads performance;
• Facebook Ads performance;
• landing page updates;
• campaign strategy;
• lead quality;
• service targeting;
• budget direction;
• lead-flow improvements;
• scheduled strategy check-ins.

The DunaHub Growth Package combines managed lead generation with the CRM and sales workflow.

The Growth Manager channel exists so campaign discussions do not become mixed with technical product requests.

Who receives access to the Growth Manager channel?

The Growth Manager tab appears only for organizations subscribed to a Growth Package tier.

The Growth tiers may include:

• Starter;
• Plus;
• Premium.

These are Growth Package tiers and should not be confused with the standard DunaHub Starter CRM plan.

A business using only Free, Starter, or Pro software does not automatically receive the dedicated Growth Manager channel.

Upgrading to an eligible Growth Package unlocks the tab.

What should be sent to the Growth Manager?

Use the dedicated channel for questions such as:

• Why did cost per lead increase this week?
• Can we prioritize another service?
• Are the leads coming from the correct locations?
• Should the campaign budget change?
• Can the landing page headline be updated?
• Why are leads not becoming proposals?
• Should we use Google Ads or Facebook Ads?
• Can we add another qualification question?
• Which service has the strongest lead quality?

The Growth Manager can also use the channel for weekly or bi-weekly strategy discussions, depending on the plan and service arrangement.

What should not be sent to the Growth Manager?

Technical platform problems should remain in general Support.

Examples include:

• login failure;
• billing problem;
• broken proposal;
• missing invoice;
• user access;
• QuickBooks error;
• WhatsApp connection issue.

Keeping the channels separate helps the right team review each request.

What happens during Growth strategy check-ins?

Growth Package organizations may receive weekly or bi-weekly strategy calls.

A useful check-in can review:

• media spend;
• leads generated;
• cost per lead;
• lead quality;
• response time;
• proposals;
• jobs booked;
• lost opportunities;
• landing page performance;
• campaign changes.

The business should prepare operational information before the meeting.

Advertising platforms show clicks and form submissions, but the CRM must show what happened after the lead arrived.

Before a check-in, review:

• how many leads received a response;
• how many were qualified;
• how many received a proposal;
• how many booked;
• why others were lost.

This helps the Growth Manager distinguish an advertising issue from a sales-process issue.

What is not handled through general Support?

General Support does not provide unlimited custom development or marketing consulting.

Custom development

DunaHub Support does not write custom scripts or integrations directly for individual accounts.

Examples include:

• a private API integration;
• custom accounting sync;
• custom website application;
• specialized automation;
• unique external-system connector.

For larger custom projects, Support can help direct the request to the DUNA agency team for evaluation.

Custom work may require:

• separate scope;
• technical review;
• estimate;
• development timeline;
• additional cost.

Marketing strategy on non-Growth plans

General Support can explain how DunaHub features work.

It does not replace a marketing agency or dedicated campaign strategist.

For example, Support can explain how to create a public form.

It does not provide ongoing non-Growth advice about:

• advertising budgets;
• campaign optimization;
• keyword strategy;
• creative testing;
• landing page conversion strategy.

These topics belong to the Growth Manager channel under an eligible Growth Package.

What should users do during a platform-wide outage?

When the entire platform appears unavailable, the status page is usually faster than opening a normal support conversation.

A platform-wide outage may involve:

• login unavailable for several users;
• dashboard inaccessible;
• widespread error pages;
• multiple features unavailable simultaneously.

Use the status page linked near the bottom of the DunaHub dashboard to check for:

• active incidents;
• investigation updates;
• affected services;
• recovery progress.

Outside business hours, urgent system-wide outages are handled by the on-call team.

A status page helps the team publish one current update for every affected organization.

How can users tell whether the problem is system-wide?

Before assuming a full outage, perform a few quick checks.

Check another page

Determine whether:

• the entire dashboard is unavailable;
• one feature is affected;
• one record produces the error.

Ask another team member

Confirm whether someone else experiences the same problem.

Try another browser

Use a private window or another browser.

Check the internet connection

Open another website.

Review the status page

Look for a published incident.

Capture the error

Take a screenshot before refreshing if possible.

If only one user or feature is affected, send the details through Support.

If the entire platform is unavailable and the status page reports an incident, follow the updates there.

What troubleshooting can users try before contacting Support?

Simple checks may solve some issues immediately.

Refresh the page

A temporary loading issue may disappear after refresh.

Sign out and back in

This can refresh the user session.

Try private browsing

Private mode helps identify browser cache or extension problems.

Disable interfering extensions

Privacy, script-blocking, password, or translation extensions can affect pages.

Try another device

This helps determine whether the issue is device-specific.

Confirm permissions

The user may not have access to the required organization or feature.

Review plan limits

A button may be disabled because the plan limit was reached.

Check integration status

For QuickBooks, WhatsApp, email, Stripe, or Twilio, confirm the connection before recreating records.

Review the documentation

The feature may require an activation step or setting.

Contact Support after these checks if the issue remains.

Do not delete records or disconnect integrations repeatedly unless the documentation or Support instructs you to do so.

How should screenshots be prepared?

A useful screenshot should include enough context to understand the problem.

Include:

• page title;
• error message;
• relevant status;
• button or field;
• surrounding interface.

Avoid cropping so tightly that the team cannot identify the screen.

Before sending, review the image for:

• passwords;
• private keys;
• payment information;
• customer documents;
• unnecessary personal data.

Never send passwords, full card details, authentication codes, or secret integration keys through support chat.

If Support needs account verification, follow the secure process provided by the team.

How should integration problems be reported?

Integrations often require more precise details.

QuickBooks

Include:

• current connection status;
• affected customer or invoice;
• error text;
• time of sync attempt;
• whether new records or all records are affected.

Review the QuickBooks integration guide before disconnecting.

WhatsApp

Include:

• whether the QR code was scanned;
• whether the status shows connected;
• whether inbound, outbound, or both directions fail;
• approximate time;
• whether one or all conversations are affected.

Stripe

Include:

• whether Stripe Connect is active;
• invoice status;
• payment status;
• error message;
• whether the customer was charged.

Do not send complete card information.

Twilio or SMS

Include:

• phone number configuration;
• whether credits are available;
• delivery error;
• message direction;
• timestamp.

Email

Include:

• provider;
• whether IMAP or SMTP fails;
• error text;
• whether sending, receiving, or both are affected.

Do not send the mailbox password in the support conversation.

How should billing questions be submitted?

For billing questions, include:

• organization name;
• current plan;
• charge date;
• amount;
• last four digits of the card only when necessary and requested;
• what you expected;
• what appeared instead.

Examples:

• charged after intended cancellation;
• upgrade not activated;
• invoice or receipt request;
• payment failure;
• plan change;
• card update;
• organization ownership transfer.

Avoid sharing full payment-card details.

How can support history help with team continuity?

Because the support channel belongs to the organization, it can become a useful record of previous solutions.

Before opening a new issue, team members can review whether the subject was discussed previously.

This can help when:

• a token expires again;
• a similar import error returns;
• a new employee needs setup instructions;
• a billing question was already answered;
• an integration requires periodic reconnection.

The company should still maintain internal procedures for recurring tasks.

Support history is useful context, but it should not be the only place where essential company processes are documented.

Who should be responsible for support requests?

Small teams may allow several users to send questions, but one person should coordinate complex issues.

This reduces:

• duplicate requests;
• conflicting information;
• repeated troubleshooting;
• unclear ownership.

A practical structure is:

Product owner

Coordinates feature and workflow questions.

Billing owner

Handles subscription and payment discussions.

Integration owner

Maintains WhatsApp, QuickBooks, Stripe, Twilio, or email connections.

Growth contact

Communicates with the Growth Manager about campaigns.

A small company may have one person performing all four roles. The important part is knowing who should respond.

How can teams avoid unnecessary support requests?

Support is more effective when the company follows a consistent operating process.

Use individual logins

Do not share passwords among employees.

Keep organization information updated

Review:

• owner;
• billing contact;
• user access;
• phone;
• email;
• integrations.

Remove former users

Revoke access when someone leaves.

Test features before launching

Test:

• forms;
• booking;
• webchat;
• missed-call text-back;
• payment links;
• automations.

Document internal workflows

Explain:

• who handles leads;
• how stages are used;
• who creates invoices;
• who changes settings.

Review plan limits

Understand when Free or Starter limits may block an action.

Read feature guides

The documentation answers many setup questions immediately.

Example: support request for an automation

A company configures an automatic follow-up after three days, but the message does not send.

A complete request could say:

Our Proposal Sent automation did not send. The lead entered the stage on June 20 at 2:15 PM Eastern Time. The automation is active, uses SMS, and has a three-day delay. We have 84 SMS credits. The lead has not changed stages. I attached screenshots of the automation and lead timeline.

This gives Support enough information to review:

• trigger;
• stage;
• channel;
• delay;
• balance;
• lead movement;
• date and time.

Example: support request for webchat

The live chat bubble appears on desktop but not on mobile Safari. We installed the snippet once in the website footer. It works in Chrome on Android. The affected device is an iPhone running the latest Safari version. I tested in private mode and attached screenshots.

This identifies:

• feature;
• website installation;
• working environment;
• failing environment;
• troubleshooting already completed.

Example: Growth Manager request

We received 26 leads from the gutter-cleaning campaign this month. Eighteen were inside our service area, nine received estimates, and two booked. Most lost leads said they expected a lower price. Can we review the ad message and landing page so the service scope and starting price are clearer?

This gives the Growth Manager campaign and CRM information, making the conversation more useful than asking only:

Why are sales low?

How should urgent issues be prioritized?

Not every issue has the same impact.

High priority

• entire platform unavailable;
• all users unable to sign in;
• widespread payment problem;
• company inbox completely unavailable;
• serious security concern.

Medium priority

• one integration stopped;
• several records fail;
• key workflow unavailable;
• booking page not accepting customers.

Normal priority

• how-to question;
• feature request;
• minor display problem;
• configuration guidance;
• non-urgent billing question.

Describe the actual impact rather than writing “urgent” without context.

Example:

Our booking page has been unavailable since 9:00 AM, and customers cannot schedule any services.

This explains why the request is time-sensitive.

Does Support provide onboarding?

General Support can answer product questions and guide users through documented features.

A business can request help understanding:

• pipeline setup;
• forms;
• booking;
• jobs;
• proposals;
• inbox;
• integrations.

However, full custom implementation, extensive process consulting, and private development may require a separate service.

A practical self-guided onboarding process is:

1. Configure organization settings;
2. Invite users;
3. Create pipeline stages;
4. Import leads;
5. Connect communication channels;
6. Test proposals and jobs;
7. Publish forms or booking;
8. Contact Support when a specific question appears.

Can users request new features?

Yes.

Feature requests can be sent through Support.

A helpful request should focus on the underlying problem.

Use this format:

Current problem: Technicians complete jobs but the office cannot see completion photos in the customer timeline.

Current workaround: Photos are sent in a separate WhatsApp group.

Desired result: Allow technicians to attach photos directly to the completed job.

Frequency: This happens on approximately 40 jobs per month.

This format gives the product team more information than only naming a feature.

A request does not guarantee immediate development or a specific release date.

Can Support build a custom integration?

Not through normal product support.

The general Support team cannot create custom scripts or private integrations for one account as part of the standard subscription.

For larger development needs, the team may refer the request to the DUNA agency.

The project would need to be reviewed separately based on:

• scope;
• technical feasibility;
• security;
• maintenance;
• timeline;
• cost.

This keeps standard product support focused on the documented platform.

What should a company do after an issue is resolved?

After receiving the solution:

1. Test the feature;
2. Confirm that the expected result occurs;
3. Inform affected employees;
4. Document recurring steps;
5. Update internal procedures;
6. Monitor whether the problem returns.

Reply in the same support conversation to confirm the outcome.

Example:

Reconnecting QuickBooks solved the problem. We created a new test invoice, and it synced correctly. Thank you.

This tells the support team that the issue can be considered resolved.

Support checklist

Before sending a request, confirm:

• The affected feature is named;
• The expected result is explained;
• The actual result is explained;
• Steps to reproduce are included;
• Date and time are provided;
• The time zone is included;
• A screenshot is attached when useful;
• Browser or device is mentioned when relevant;
• The connection status was checked;
• Another user or device was tested when possible;
• No password or secret key is included;
• The correct channel is selected;
• Platform-wide outages were checked on the status page;
• Growth strategy questions were sent to the Growth Manager channel.

Summary: how does DunaHub Support work?

DunaHub provides an in-app Support channel inside the dashboard.

The channel can be used for:

• account questions;
• billing;
• plan changes;
• ownership transfers;
• how-to guidance;
• bug reports;
• feature requests;
• integration assistance.

The conversation is stored at the organization level, allowing authorized team members to review and reply.

The typical response time is the same business day during U.S. business hours. Non-urgent messages sent outside business hours are normally handled the next business day.

Growth Package organizations also receive a dedicated Growth Manager channel for:

• advertising campaigns;
• landing pages;
• lead-flow strategy;
• performance reviews;
• weekly or bi-weekly check-ins.

Platform-wide outages should be checked through the status page, while normal account and product issues should be sent through Support.

General Support does not include custom development or marketing strategy for non-Growth organizations.

Frequently Asked Questions

Where is the Support channel?

Open the DunaHub dashboard sidebar and select Support below the Growth section.

Is Support available on Free?

Yes. General product and account Support is available across the standard plans.

How do I send a message?

Type the question in the box and press Enter. Use Shift + Enter to add a new line.

How do I know when Support replies?

An unread-count badge appears beside the Support entry.

Can other team members see the conversation?

Yes. The conversation is saved per organization and can be viewed by authorized dashboard users.

What is the typical response time?

The typical response is the same business day during U.S. business hours.

What happens outside business hours?

Non-urgent requests are generally answered the next business day.

What should I do during a full platform outage?

Check the status page linked from the bottom of the dashboard.

Can I report bugs?

Yes. Describe the problem, expected result, steps, time, and attach a screenshot when possible.

Can I request a new feature?

Yes. Explain the business problem, current workaround, and desired result.

Can Support help with QuickBooks?

Yes. Integration help can include QuickBooks, Twilio, Stripe, and WhatsApp.

Does Support provide custom coding?

No. Custom scripts and integrations are not included in normal Support. Larger projects may be referred to the DUNA agency.

Does general Support provide advertising strategy?

Not on non-Growth plans. Campaign strategy belongs in the Growth Manager channel.

What is the Growth Manager channel?

It is a dedicated channel for Growth Package clients to discuss ads, landing pages, lead flow, and campaign performance.

Does the standard Starter CRM plan include a Growth Manager?

No. The Growth Manager belongs to eligible Growth Package tiers, which are separate from the standard CRM plans.

Can I send screenshots?

Yes. Screenshots are recommended when reporting a visual error or unexpected behavior.

Should I send my password?

No. Never send passwords, card details, authentication codes, or secret keys through Support.

Can I continue an old conversation?

Yes. The support history remains connected to the organization.

What information makes a support request faster?

Include the feature, expected result, actual result, steps, date, time, time zone, screenshot, and affected users or records.

Get help directly from your dashboard

Questions should not remain unresolved simply because a small business does not have an internal technical department.

Create your DunaHub account, open Support from the dashboard, and contact the team whenever you need help with your account, integrations, or platform workflow.