DH Connect Handbook

Start here: your first day with DH Connect

Go from a new account to a published card and a simple follow-up routine, without learning everything at once.

Before you start

An email address and password for your DH Connect account.

Your name, contact details, and a clear idea of who you want to help.

Create your account

Create your account at https://dhconnect.io/sign-up using Email + Password. Sign in again at https://dhconnect.io/sign-in with the same email and password. If invited, start with the invitation link and review the displayed sponsor before submitting Account Setup.

Build and manage cards at https://dhconnect.io/studio. After publishing, copy your visitor link from the app: https://dhconnect.me/[slug]. Replace [slug] only with your actual published handle. Never share your private Studio address with visitors.

A DH Connect signup is not proof of membership in another business or program.

Know the three jobs of your card

Front Door introduces you and gives visitors a reason to continue. The Hook asks a useful question with a small set of answers. The Close gives each answer a relevant next step. Setup contains the settings behind those pages.

Example: introduce your service, ask which problem the visitor wants to solve, then offer the appropriate information or contact action. Use truthful, specific wording rather than claims you cannot support.

Build one simple card

Open Studio and choose Create New Card. Give the card a useful internal name, then work through Setup, Front Door, The Hook, and The Close. Start with one clear goal rather than trying to include every offer you have.

Private draft saves are separate from publishing. Wait for saves and uploads to finish, and correct any red field messages before continuing.

Publish and check the visitor experience

Choose Publish Card only after reviewing every defined answer and next action. Copy the public URL shown after publishing and open it in a private browser window. Test the card on your phone as well.

A contact button may open another app or prepare a message. That does not mean the visitor sent the message. Test the final destination, not just the appearance of the button.

Begin a simple routine

Share your published card with a relevant audience. Check Pipeline for genuine submissions, use tags to organize them, and follow up based on what the person actually shared. Check Inbox for internal requests.

Add Member Spotlight and Team Command to your routine when they are relevant. You do not need to master every area before sharing your first card.

Success checklist

You can sign in with the same DH Connect email/password account.

One card is published and its public link works signed out.

You know where to find genuine submissions and internal requests.

Tips

Keep your first card focused on one audience and one useful outcome.

Use the launch checklist before sending the link widely.

I land on Account Setup instead of Studio.

Finish the required account setup first. Private workspaces require a signed-in account with setup completed.

Find your way around the workspace

Understand what belongs in Studio, My Media, Pipeline, Member Spotlight, Team Command, Inbox, and Account Info.

Before you start

A signed-in account.

Use Studio for your digital cards

Studio is where you create and edit cards. Card Editor works on the selected card; Card Vault manages your saved cards. Check the Card Name selector before editing so you do not change the wrong draft.

Use My Media for reusable images

My Media holds your photos and reusable carousels. Naming them clearly makes it easier to choose the right asset later. Selecting a saved carousel copies its content into your card; future card edits do not automatically rewrite the original reusable carousel.

Separate prospects from team members

Pipeline is for genuine submissions and follow-up. Team Command is for your attributed team and its activity. A person viewing a card or submitting a first name is not automatically a team member.

Member Spotlight has its own published profile/card experience and includes Member Card Studio. It is separate from the standard Studio card editor.

Check Inbox and Account Info

Inbox holds private internal requests, not a full live-chat service. Account Info is where you maintain the basic identity and contact details used by the system. Changing a contact email there does not necessarily change the sign-in identity used to sign in.

Understand smaller-screen navigation and availability

On narrower screens the sidebar becomes an icon rail. Each destination has an accessible name; use the icon labels or titles to identify it. This Help Center is available from the workspace settings links.

Items marked Coming Soon are not live features you need to configure. Development previews or owner-only Demo View may look different from an ordinary member account.

Success checklist

You can select the right workspace for a task.

You can distinguish your selected Studio card from a Member Spotlight variant.

Tips

Bookmark the Help Center for quick reference.

A demo label means sample presentation data, not genuine leads or team activity.

A section asks me to sign in.

Private workspaces require authentication. Sign in with the DH Connect email/password account you used to create your DH Connect account.

Create your first card, step by step

Follow the complete standard builder journey from naming a card to checking its published link.

Before you start

Complete Account Setup.

Prepare a short introduction, a visitor question, and at least one useful next action.

Create and name your card

Open Studio and select Create New Card. Enter a recognizable internal card name and choose Save Card. If the new-card dialog offers Autofill Data or Start Fresh, choose the option that matches how much existing information you want to reuse.

The internal card name helps you organize your work. It is not the same thing as the public URL or the visitor-facing headline.

Complete Setup

Review the basics drawn from Account Info. Use Account Info to correct those shared details. Configure the selected card's contact destination and public-contact settings, then test the destination when the test action is available.

Choose a valid, available public handle when the builder asks for it. A handle must begin with a lowercase letter or digit and use lowercase letters, digits, or hyphens, up to 40 characters. System paths and handles owned by others cannot be used.

Write Front Door and The Hook

On Front Door, introduce who you help and why the visitor should continue. On The Hook, choose your media, write one clear question, and define meaningful answers.

For example, a service provider might ask whether the visitor wants pricing, examples, or a conversation. The choices should describe real visitor intentions, not three versions of the same slogan.

Complete every defined Close

Open The Close and review the editor for each answer you actually defined in The Hook. Match the media, message, and next action to that answer. Do not assume editing one Close updates the others.

Use accurate button text. A button that opens a booking page should say that, rather than suggesting a booking is already confirmed.

Review, publish, and test

Check the preview and use Continue where required to validate each stage. Correct highlighted errors. Choose Publish Card explicitly when you are ready.

Open the public URL signed out and walk through every answer path. Confirm that media loads, your contact visibility is right, and destinations work on a phone. Keep the launch checklist open while you test.

Success checklist

The intended card is selected.

All defined visitor paths are complete.

The public card works outside your signed-in editing session.

Tips

Draft saves protect unfinished private work but do not make it live.

If all five card slots are in use, review Card Vault before creating another card.

Publish Card is disabled.

Open the card in Card Editor, select a card, and wait for current saves or uploads to finish. Then resolve any validation errors shown by the builder.

My preferred handle is unavailable.

Use another clear variation, such as your name plus a descriptive word. Do not assume a card title reserves a public handle.

Write a Front Door visitors understand

Make your opening page specific, credible, and easy to continue from.

Before you start

A card open in Card Editor.

Choose one audience

Decide who the card is for before writing. A card for first-time customers needs different wording from a card for potential collaborators. If you serve very different audiences, a separate card may be clearer than one page that tries to address everyone.

State a useful reason to continue

Open Front Door and make your main message describe the help, information, or conversation the visitor can expect. Prefer concrete language such as 'Find the right service for your next project' over unsupported promises about income or guaranteed results.

Keep the next step honest

Choose the available button treatment and wording that fit your brand. The label should describe what happens next, not imply that a sale, result, or signup has already happened.

Front Door leads into your card journey. Make sure its promise matches the question and choices on The Hook.

Read it as a first-time visitor

Use the card preview on this content step. Check the smallest screen you expect people to use. Remove repeated words, long explanations, and claims you cannot verify.

Continue to validate the stage when required. Changing tabs or autosaving a draft is not the same as completing a stage or publishing it.

Success checklist

A new visitor can tell who the card is for.

The opening promise matches the next page.

The button text describes a real action.

Tips

Write the full idea first, then shorten it.

Choose clarity over clever wording when the two conflict.

I cannot find a visitor preview in Setup.

Setup is for private configuration. Visitor previews belong on the card-content steps such as Front Door.

Build a Hook with useful answer choices

Ask a question that helps visitors choose their own relevant next step.

Before you start

A card with Setup completed.

A clear idea of the visitor's likely needs.

Choose the supporting media

Open The Hook and use Choose Your Hook Media. Choose Photo, Video, or Carousel as appropriate. Add only media you own or have permission to use. A useful image can work well; a video is not required.

Check the chosen aspect ratio and the whole-image preview. Keep important faces and text visible. For externally hosted media, test the actual public watch experience.

Ask one answerable question

Use Your Hook Question to ask what would help the visitor now. For a local service, 'What would you like help with?' is clearer than a question that assumes the person already wants to buy.

Do not ask for private financial, medical, or other sensitive information in casual card answers. Keep the question focused on an appropriate next conversation.

Define distinct choices

In Choice, enter concise answers that represent different needs. For example: 'See the options', 'Understand the process', and 'Ask a question'. These are examples, not requirements; use wording that fits your actual offer.

Only defined choices belong in the Close editors. If you remove or rename an answer, revisit its Close before publishing.

Match each answer to The Close

Continue to The Close and check each answer's media, message, and action. A visitor who asks for information should not unexpectedly land in an unrelated signup or contact flow.

Preview every choice instead of testing only the first answer. The question, answer label, and next action should make sense together.

Success checklist

The question is easy to answer.

Choices represent distinct visitor needs.

Every defined choice has a relevant Close.

Tips

Use plain answers, not internal tag names.

Choice Auto Tags organize later activity; they do not replace clear visitor-facing wording.

A Close editor is missing.

Check whether its corresponding Hook choice has been defined. The Close is choice-specific.

The photo looks wrong.

Check the source image and aspect ratio, then preview on a phone. Use a high-quality image without critical details at the edges.

Give every answer the right Close

Set up choice-specific messages, media, and contact or connection actions.

Before you start

Define your Hook choices first.

Open the matching choice editor

Go to The Close and expand the editor for a defined Hook answer. Work through one answer at a time. This is a choice-specific editor, not one shared ending for every visitor.

Answer the visitor's selected need

Write a brief message that follows naturally from that answer. Explain what the visitor will get by taking the next step. If the person chose pricing information, help them understand how to obtain pricing rather than repeating your introduction.

Avoid invented testimonials, proof, urgency, or guarantees. Use information you can stand behind.

Choose the action and destination

Use the available layout and action settings for that choice. Check the contact channel or link carefully. A message handoff may prepare text, but the visitor still needs to send it in the destination app.

If you use a form or connection option, review the fields and wording it presents. A request for one response is not blanket permission to add someone to a mailing list.

Review media and repeat for the other answers

Check the photo, carousel, or other media attached to this Close. Reusable assets and media used on The Hook are not a substitute for reviewing this choice's own content.

Repeat for every defined answer, validate the step, and publish explicitly when all paths are ready. Test the published path as a signed-out visitor.

Success checklist

Each defined answer has its own coherent ending.

Buttons lead to the intended destinations.

No wording suggests an unconfirmed message, booking, or outcome.

Tips

One useful action is usually easier to understand than several competing requests.

Republish after changing a live card's Close.

A change appears under one answer but not another.

That is expected for choice-specific settings. Open the other answer's editor and update it separately if needed.

A prepared chat message was not sent.

Opening a messaging app is only a handoff. The visitor must send the message; DH Connect cannot treat the handoff as confirmed delivery.

Save, preview, publish, and update a card

Understand the difference between private drafts and the version visitors can actually see.

Before you start

A card open in Card Editor.

Treat draft saving as private work

Signed-in unfinished work can autosave as a private draft. Watch for save status and finish current uploads before leaving. An error message means you should resolve the issue rather than assume the latest change was saved.

Draft saving does not publish a new card or replace the current published version. Completing a stage and publishing are also separate actions.

Preview the complete journey

Review Front Door, The Hook, and every defined Close. Check text, images, contact details, and destinations. Use the launch checklist to avoid forgetting an answer path or a public-contact setting.

If the builder highlights a problem in red, follow its correction instructions. It may move you to the section that needs attention.

Publish explicitly

With the intended card selected in Card Editor, choose Publish Card. Wait for the confirmed result. Do not repeatedly click while the request is working.

If a handle is unavailable or a required field is incomplete, choose another valid handle or correct the marked field. A private draft title does not establish public URL ownership.

Verify the public result

Use the public URL shown after publishing. Open it in a private or signed-out browser window and check every path. For contact buttons, verify the destination app or page and understand which final action the visitor must perform.

After future edits, publish again to apply them to the live card. Social sites may continue showing an older cached link preview even when the card itself has changed.

Success checklist

Publishing has a confirmed success result.

The public URL shows the intended content signed out.

You know that later draft edits require republishing.

Tips

Keep a copy of the exact published URL.

Check the public page itself separately from a social app's preview image.

The public card still shows old wording.

Confirm you edited the correct card and republished successfully. Reopen its exact public URL in a fresh private window.

I am unsure whether publishing succeeded.

Wait for the request to finish, read any message, and inspect the public link before trying again. Do not infer success from a click alone.

Organize, rename, switch, and delete cards

Use Card Name and Card Vault without confusing internal names, public links, or card variants.

Before you start

At least one saved Studio card.

Select the card you mean to edit

In Studio, use the Card Name selector. Confirm the selected card before changing content or publishing. Card Editor operates on that selection; Card Vault gives you a management view.

Use descriptive internal names

Open the card's naming control in Card Vault, enter a helpful name, and choose Save Name. Good internal names identify an audience or purpose, such as 'New customer questions' or 'Event introduction'.

Renaming your internal card is not the same as changing its public handle, profile name, or headline. Keep those identities distinct.

Work within the available slots

The standard Studio currently provides five card slots. When they are all in use, Create New Card is unavailable. Review existing cards before deciding whether to remove one.

Do not delete a working card just to experiment if it has an important public link. Editing the correct private draft may be enough.

Delete only after checking the consequences

Use the Delete action inside Card Vault for the specific card, then read the confirmation carefully. Confirm only if you intend to remove that card. Deletion is not a temporary pause or a way to unpublish safely for later.

Cancel if you are unsure. Keep a written copy of important content and check where you have shared the public link before deleting a card. Do not assume deleting a card erases every historical record elsewhere.

Success checklist

You can identify the selected card before editing.

Internal card names describe their purpose.

You understand a deletion before confirming it.

Tips

Studio Card Vault and the Member Spotlight card/variant tools are different areas.

Wait for a save or upload before switching cards.

Publish Card is unavailable in Card Vault.

Open the intended card in Card Editor to publish it.

My renamed card still has the same URL.

An internal rename does not automatically change the public handle. This separation protects existing links.

Share your card and test what recipients see

Share the right link, understand previews, and check the experience outside your own account.

Before you start

A successfully published card.

Copy the published card link

Use the URL shown for the published card rather than copying your Studio address. Studio is an editing workspace and requires sign-in. Your public card is designed for visitors.

dhconnect.io is the marketing and dashboard hub. dhconnect.me is the clean-link card runtime. Your referral invitation link has a different purpose from your public card link.

Add a useful introduction

When sharing in a message, profile, or post, explain why the recipient might want to open the card. For example: 'Here are the options we discussed—choose the one you want to know more about.'

Use an appropriate audience and respect community rules. Sharing a card does not give permission for unsolicited bulk follow-up.

Check the signed-out experience

Open the exact link in a private browser window and on a phone. Go through the opening, each Hook answer, and each Close action. Check that images load without your creator session.

If a destination needs another app, test it on a device with that app where possible. A desktop browser may behave differently from a phone.

Keep previews in perspective

Social and messaging apps can cache titles and images. Publish your latest card changes first, then use the current share link provided by the app. A stale social thumbnail does not by itself mean the card failed to update.

Do not add private visitor information to link text or preview images. Share only the content you intend the public to see.

Success checklist

Your shared URL opens a public card, not an editor.

Recipients understand why you sent it.

All visitor paths work without creator authentication.

Tips

Card links, referral links, and workspace links are not interchangeable.

Test before placing a link on printed material or a permanent profile.

The recipient is asked to sign in.

Check that you shared the published card URL rather than /studio, /pipeline, or another private workspace.

A social preview is out of date.

Check the actual card in a fresh window, confirm it is republished, and use the current sharing option. The external app controls its cached preview.

Upload, name, and reuse photos

Keep your photo library useful and resolve ordinary upload issues without losing track of your card.

Before you start

A signed-in account.

An image you own or have permission to use.

Choose a suitable image

Use a clear, readable image with enough resolution for a phone screen. Avoid placing essential text or a face at the extreme edge. Do not upload private customer documents or personal information that should not be public.

Photo uploads are optimized by the app. The optimized image must be 8 MB or smaller; the storage indicator shows your current account usage.

Upload from My Media or a card media control

Open My Media and choose the photo upload control, or use the upload option in the card's media editor. Select your image and wait for completion before switching cards or leaving the page.

If the app shows 'Upload failed, please try again', retry manually after checking your connection and file. Do not assume the unsuccessful file has been queued for later.

Name and select the correct photo

Give reusable photos recognizable names. When a card offers the My Media picker, choose the intended item and review the resulting preview. Verify the image belongs in the selected stage, not just somewhere in the card.

If a naming action fails after an upload, read the message and correct the name separately where available. A naming failure is not necessarily an upload failure.

Check the published result before sharing

Preview the selected aspect ratio and publish the card when ready. Open the public card signed out to confirm visitors can see the image, including any choice-specific Close photo.

Before deleting a library image, review where you use it. Do not assume removing media is a harmless way to free storage for cards that are already shared.

Success checklist

The upload has completed.

The correct photo appears in the correct card stage.

The published image is visible signed out.

Tips

Use the library Refresh action if the list needs updating.

Follow the current storage indicator rather than assuming unlimited storage.

An upload keeps failing.

Check that you selected a supported image, try a smaller image, confirm available storage and connection, then retry manually.

The image appears in Studio but not publicly.

Confirm you published the intended card after selecting the image. Test the exact published link signed out and note which stage fails.

Build and reuse a photo carousel

Choose, order, and review a short series of images without changing your reusable source accidentally.

Before you start

Photos ready in your device or media library.

Decide what the sequence should explain

Use a carousel when a short sequence communicates better than one image: options, steps, examples, or a concise introduction. Put the most useful image first and keep words large enough for a phone.

Use only accurate examples and permitted images. A carousel does not turn a hypothetical result into verified proof.

Add the images

In the card's media settings, choose Carousel. Use the available upload or My Media selection controls. Batch selection can add up to six images at once and fills empty slides without replacing existing photos.

Wait for uploads to finish. Review each slide, including empty slides that may need an image or removal.

Set the order and framing

Use the move-up and move-down controls to arrange slides. Check the selected aspect ratio and preview each image. Remove unnecessary slides so the sequence has one clear purpose.

Do not place a long instruction on a slide that requires the visitor to zoom to read it. Put essential next-step wording in the card text as well.

Understand reusable copies

My Media includes reusable carousel tools. Selecting a reusable carousel into a card copies its content. Changes to the card copy do not automatically edit the library source; renaming the card's media does not rename that source either.

If you want a change in multiple cards, review and update the relevant copies explicitly, then republish those cards.

Success checklist

Every slide is intentional and readable.

The order makes sense on a phone.

You know whether you edited a reusable source or a card copy.

Tips

Keep a carousel short enough to scan.

Review carousels separately on The Hook and each Close where you use them.

My reusable carousel did not change after editing a card.

That is expected. The card uses a copy. Edit the reusable source separately if that is your intention.

Some slides are empty.

Add an image or remove the unused slide, then resolve any highlighted validation messages.

Use existing video links and external media

Add media you already have and understand why some providers open a direct-watch card instead of an embedded player.

Before you start

A publicly watchable link to existing media you have permission to share.

Use an existing public watch link

Choose Video in the appropriate card media settings and enter the supported watch link. Use a link visitors can open, not a private creator-dashboard or edit URL.

DH Connect does not currently provide completed direct video uploads through the disabled video-upload flow. Use the existing link-based media controls instead. This written lesson does not require you to create a video.

Choose the correct presentation

Set the aspect ratio that matches your media and check the preview. Tall and wide media have different space needs. Do not judge the experience solely from your signed-in provider account.

Expect direct-watch behavior for some providers

Meta Reels and TikTok use direct-watch cards rather than unreliable mobile iframe playback. A visitor may need to open the provider to watch. That is intentional, not evidence that your card is broken.

Other external providers may restrict embedding, require sign-in, or change playback behavior. You control your card and link, not the provider's policies.

Test as the visitor

Publish and test the exact card signed out, including on a phone. Confirm the media is public, the link is correct, and the provider can open.

If playback fails, check the provider's own watch page first. If the link no longer works, replace it in the correct card stage and publish again. A photo or carousel is a valid alternative.

Success checklist

The public watch link is correct.

The media remains usable outside your own provider login.

The visitor understands when an external provider opens.

Tips

Avoid depending on one external platform for all essential information.

Keep the main message understandable even if a visitor does not play the media.

TikTok or a Reel opens outside the card.

That direct-watch behavior is intentional. Test that the destination is the media you intended.

The media plays for me but not others.

Check public visibility, regional/account restrictions, and embedding permissions at the hosting provider.

Control public contact details and contact buttons

Keep public visibility separate from private account information and test where messages actually go.

Before you start

Correct contact details in Account Info.

Review your shared account details

Open Account Info to review your name, email, and phone. Enter information you intend the system to use. The account's public-contact switch provides a default, but individual cards have their own visibility controls.

Set visibility for the selected card

Open the card's Setup and review Make E-mail public and Make phone public separately. These card settings override the general Account Info switch for that card.

Off keeps that detail hidden from the card. Turning a display switch off is not a promise that the information has been erased from your account or from material you previously shared elsewhere.

Understand the public AccessInfo area

Published contact details, social profiles, and community links belong in the branded header's AccessInfo dropdown. Check that area when verifying the public card instead of expecting the same details repeated throughout the card body.

Contact exports should contain the contact methods you actually published, not private creator information or visitor tracking. Review a saved contact on your own device before relying on it.

Test your contact destination

In Setup, select the intended contact channel and enter its destination in the requested format. Use the test action if available. Check each Close's action as well.

A phone or message link may open a native app or prepare a message. It does not confirm that a call connected, a message was sent, or the recipient received it.

Publish visibility changes

Publish or republish the card to apply changes to its live version. Open the public link in a private window and check the AccessInfo dropdown plus the visitor action paths.

If a social or community link is wrong, fix it in the appropriate card settings and test again. Do not publish private group invitations unless that is intentional.

Success checklist

Only intended contact methods are visible publicly.

The chosen contact destination is correct.

You understand app handoff is not confirmed delivery.

Tips

Use a business contact destination if you do not want to expose a personal one.

Check card-level switches on every card you publish.

I changed Account Info but a card still hides my email.

Review the card's own Make E-mail public setting and republish. Card-level settings override the general default.

Save Contact did not open my contacts app.

Device and browser behavior varies. Check whether a contact file downloaded, open it manually if appropriate, and review its contents before saving.

Find and understand genuine leads in Pipeline

Review submissions and recorded actions without confusing activity with identity or confirmed delivery.

Before you start

A published card and genuine visitor submissions, or an empty Pipeline to learn from.

Open your own Pipeline

Choose Pipeline in the workspace. This is the live lead area for your account. If it is empty, the app may show that no first-name submissions have arrived yet; that is a useful state, not a reason to create fictional contacts.

An owner-only Demo View may contain labeled sample data. Never treat those examples as your live prospects.

Read the information the person actually supplied

Open the relevant lead row or detail area and review the submitted name and available answers. A first name is self-reported information, not verified identity or complete contact information.

Use the context to understand what the visitor selected. Do not infer income, intent to buy, membership, or a completed conversation from a name or click.

Interpret activity within its limits

Recorded button activity can help distinguish actions on The Hook and The Close where that detail is available. Older totals may not contain the same breakdown as newer activity.

A click is not a sale, a sent message, a completed booking, or a confirmed outcome. A visit alone is not the same as a captured lead.

Organize and follow up thoughtfully

Use the available tags and follow-up tools to separate people by genuine interests or next steps. Review the actual submission before writing to anyone.

Keep your message human and relevant. Do not paste internal labels, tracking details, or assumptions about what the person did beyond the information actually available.

Refresh when needed

Use the refresh or retry action if a load fails or you want to check for new submissions. Wait for the result and read any displayed error.

If a count looks surprising, check the selected card, any active filters, and whether you are viewing live or labeled demo data before making conclusions.

Success checklist

You can locate a genuine submission.

You distinguish self-reported information and clicks from verified outcomes.

Your next action follows the person's actual request.

Tips

An empty Pipeline is normal before people submit.

Never copy private lead details into a public support screenshot.

A visitor saw my card but does not appear as a lead.

A visit is not necessarily a submission. Check what the visitor actually completed; do not assume every viewer provides a name or contact details.

Pipeline does not load.

Use the retry control, check your connection and DH Connect email/password account, and note the visible error without repeatedly submitting actions.

Use tags and a practical follow-up routine

Keep prospect organization simple and make reminders reflect your own next actions.

Before you start

A genuine lead or submission in Pipeline.

Choose a small tagging system

Open Pipeline and use its tag controls on the intended lead. Prefer useful labels such as a real interest or your next action. Too many overlapping labels make a list harder to work with.

Pipeline tags describe prospects. Team Command tags describe members in the team context; they are not interchangeable just because the names look similar.

Check the correct person and saved state

Review the lead before adding or removing a tag. Wait for the operation to finish and check the displayed result. If the app reports an error, do not assume it saved.

Avoid sensitive or speculative labels. A person's selected answer is not permission to categorize them by private characteristics.

Make the next action specific

When a follow-up tool or reminder is available, use it for an action you can actually take: respond to a question, share requested information, or check whether a conversation is still welcome.

If your reminder has a Done action, use it when you have completed the task. External automations or activity elsewhere should not be assumed to clear your own reminder.

Review a manageable set regularly

Review your follow-ups, read the submission, and use an appropriate contact channel only where you have a genuine basis to contact the person. Keep messages relevant and respect a request to stop.

Do not interpret a tracking event as proof that someone wants repeated outreach. A bounded request is not newsletter consent.

Success checklist

Tags have a clear operational purpose.

Saved tag changes are visible.

Reminders represent a concrete next action.

Tips

Use fewer tags consistently rather than many tags once.

When a tool is unavailable in your interface, do not assume an automation is running behind it.

A tag is not visible after saving.

Check for a save error, confirm the intended lead, and refresh once if appropriate. Do not keep adding duplicate tags to work around a failed save.

Understand Choice Auto Tags

Know when a Hook choice can organize Pipeline activity and when a Team tag can apply.

Before you start

Defined Hook choices and access to the relevant tagging controls.

Start with the visitor choice

In the selected card's choice settings, review the Choice Auto Tag controls associated with the answer you mean to organize. Keep the visitor-facing answer understandable; internal tagging should not make the question awkward.

Keep Pipeline and Team tags separate

A Pipeline choice tag is tied to the matching call-to-action click. A Team choice tag applies only after a new attributed signup satisfies the relevant conditions.

Selecting a Hook answer alone does not prove someone joined the team. A Team tag does not change the person's permanent sponsor.

Choose only tags you are allowed to use

Use the available authorized tag options in the correct workspace. Do not assume you can apply another person's private labels or change their team relationships.

If you rename choices or change the action, review the mapping again. Publish card changes explicitly before expecting the live card to use them.

Verify with real actions, not assumptions

Review genuine Pipeline activity or the relevant new attributed team signup. Check the actual event that triggers the mapping rather than expecting the tag at every earlier step.

Historical activity may not contain newer breakdowns. Do not invent old events to make the numbers match a new configuration.

Success checklist

The mapping matches the intended choice and event.

Team tagging is not confused with sponsorship.

You know that an answer alone is not a team signup.

Tips

Give tags names that are useful internally, not names that disclose private assumptions.

Keep a note of the intended mapping when reviewing a card.

A Team tag did not appear after a visitor chose an answer.

The Team mapping requires a new attributed signup, not just an answer or a click. Check the relevant signup and attribution before expecting the tag.

Set up and understand Member Spotlight

Use Member Spotlight and Member Card Studio while keeping publication, variants, and activity claims clear.

Before you start

A signed-in account.

Open Member Spotlight

Choose Member Spotlight in the workspace. Use its own tabs to find Member Card Studio and the relevant card or variant tools. This is a separate experience from the standard Studio card builder.

Review your current saved and published state before changing anything. Different variants can represent different content without being interchangeable public identities.

Prepare your member-facing content

Use accurate information, an appropriate photo, and links you want to share publicly. Keep your introduction useful to the person discovering you.

Do not present a badge, label, or profile as proof of income, results, identity verification, or membership beyond what it actually establishes. Verified in this context refers to verified email, not those wider claims.

Review the intended variant and publish deliberately

Check the selected variant and publication controls. Publish the intended content explicitly and open its actual public link to verify it.

Do not assume a private draft or inactive variant appears in public discovery. Active published Member Spotlights may appear on public surfaces; do not put private lead information in them.

Interpret comparisons and awards honestly

Use the available comparisons and activity summaries within their stated scope. Internal action clicks are not the same as conversions, sales, or delivered messages.

Historical totals can lack newer action breakdowns. Awards should reflect genuine eligible activity, not fictional demo records or assumed outcomes.

Success checklist

You know which Member Spotlight variant you are editing.

Only intended content is published.

You interpret public visibility and activity labels accurately.

Tips

Keep standard Studio cards and Member Spotlight variants distinct when troubleshooting.

Public discovery offers an opportunity to be found, not a guaranteed audience size.

I cannot find Member Card Studio in standard Studio.

Open Member Spotlight and use its own tabs. Member Card Studio lives there.

My draft is not in public discovery.

Review publication and active-variant state. Draft or inactive content should not be assumed publicly listed.

Share the right invitation and understand referrals

Keep referral signup links, public card links, and permanent sponsorship distinct.

Before you start

Completed Account Setup and an assigned referral identity.

Find your own permanent referral link

Use the referral link shown by your account or Team Command rather than constructing a guessed URL. A referral invitation is for someone joining DH Connect through you.

Your public card link serves a different purpose: it opens a visitor card experience. Copy the exact link the relevant area provides.

Share it with context

Explain that the link is an invitation to DH Connect and what the person can do after joining. Do not imply that following a link or creating an DH Connect account completes enrollment in another program.

Ask the invitee to start from the invitation link and review any displayed sponsor information during setup.

Understand when a member appears

Team membership is based on an actual attributed signup and sponsor relationship, not an anonymous view or a submitted first name.

An existing account or an unrelated signup should not be treated as a newly referred member merely because the person later opens your card.

Preserve the relationship

Permanent referral lineage is not a label you can replace with a choice tag. Team tags organize your team context without changing sponsorship.

If something looks wrong, collect the invitation link used and the visible setup message, without sharing private credentials. Do not attempt to fix attribution by creating duplicate accounts.

Success checklist

You shared the exact referral invitation link.

Invitees know they are joining DH Connect.

You distinguish a new attributed signup from a card interaction.

Tips

Use the same DH Connect email/password account consistently.

Do not promise a change to an existing permanent sponsor through a tag or new link.

A person clicked my link but is not on my team.

Check whether they completed a new attributed signup. A click, visit, or existing account is not sufficient.

The invite information looks wrong during setup.

Stop and check the original invitation link before submitting. Do not confirm details you know are incorrect.

Use Team Command for real team activity

Review your roster, tags, time periods, and internal outreach without overstating what activity means.

Before you start

A signed-in account; team results require genuine attributed members.

Start with the live roster

Open Team Command. An empty team is normal before people join with you as their sponsor. Use the permanent referral link shown there to invite people.

If you have an owner-only Demo View, its labeled fictional roster is for presentation. It does not change live members, referrals, awards, or deliveries.

Choose the reporting period and scope

Review the available period and tag controls before comparing members. Counts can change with the selected reporting period and scope.

Recorded app activity describes use of the system. It is not proof of business results, sales, or what happened in conversations elsewhere.

Use tags to focus on a useful group

Apply authorized team tags to organize real members and use the roster or focus tools for a smaller relevant group. Team tags and Pipeline prospect tags have different scopes.

Do not mistake a tag change for a sponsor change. Do not use private or speculative labels that would be inappropriate to disclose.

Use Connect or Rescue thoughtfully

Review a member before starting an internal request. Connect and Rescue Nudge use private recipient-owned request forms, not a live-chat channel.

Keep requests useful, respectful, and specific. The recipient's private contact details are not automatically exposed to the team. Submitting a request is not proof it was read or acted on.

Review broadcasts before approving them

Use the available Broadcast tools for the intended tagged audience. Review the actual draft, audience, and scheduling controls before approving or sending.

Team Broadcast pop-ups and phone-notification campaigns are separate channels. Ava-generated drafts, where available, require their own review and approval; do not assume a draft was sent.

Success checklist

You can identify the live team and current period.

Team tags are used without changing sponsorship.

Internal requests and broadcasts are described within their actual delivery scope.

Tips

Check Inbox for responses and requests.

Use a smaller relevant audience instead of broadcasting everything to everyone.

My team is empty.

Check whether anyone completed a genuine attributed signup with you as sponsor. Card viewers and lead submissions are not automatically team members.

A broadcast did not appear as a phone notification.

Team Broadcast pop-ups and phone campaigns are separate. Check the configured channel, audience, approval state, and recipient permissions.

Use Inbox for internal requests

Find member requests and understand the difference between an internal request and a delivered chat message.

Before you start

A signed-in account.

Open Inbox

Choose Inbox in the workspace. It is the private area for requests directed to you, including relevant Connect or Rescue flows.

An empty inbox can simply mean no requests have been received. It is not the same data as visitor submissions in Pipeline.

Read the request before responding

Review the sender information, message, and any optional social profiles or reply details supplied. A supplied profile or name is context, not an independently verified identity claim.

Do not assume a sender has access to your private contact details just because they can send an internal request.

Choose the appropriate next action

Use only the reply or contact options actually available in the request. If an option opens an external app, review the destination and complete the action there yourself.

Connect and Rescue Nudge are request forms rather than live chat. Do not expect a continuous chat thread or a confirmed delivery receipt unless the interface specifically provides one.

Keep private information private

Avoid forwarding screenshots that show other people's request text or contact details. If you need help with an error, redact private information and record the page and action that failed.

Review requests at a pace that works for you; there is no need to treat every activity prompt as an urgent obligation.

Success checklist

You can distinguish Inbox requests from Pipeline submissions.

You review optional contact details before acting.

You do not equate a request or handoff with a completed conversation.

Tips

Use the sender's actual question to guide your reply.

Respect a person's preference not to continue a conversation.

I cannot find a visitor's name here.

Check Pipeline for visitor submissions. Inbox is for internal requests, not a duplicate lead list.

I expected a chat conversation.

The current Connect and Rescue flows are private request forms. Use the available next action rather than expecting live chat.

Update Account Info without confusing sign-in

Maintain your basic profile and understand which settings apply to an individual card.

Before you start

Sign in with your existing DH Connect email/password account.

Open Account Info

Use Account Info in the workspace settings. Review the displayed name, email, phone, and other available basic fields.

Use accurate information. Do not publish a personal email or phone unless you intend visitors to have it.

Save the updated details

Edit the intended fields and choose Save Account Info. Wait for the saved confirmation or resolve any error. A typed value is not a confirmed saved change.

If Studio shows shared basics as read-only, return to Account Info to correct them instead of trying to edit them in that card's Setup summary.

Check public visibility per card

Review the account's public-contact preference, then inspect each card's Make E-mail public and Make phone public settings. Card settings override the general preference for that card.

Review and republish any card whose visitor-facing details should change. Do not assume an account save automatically republishes every public card.

Keep sign-in and contact details separate

Your account contact email and the sign-in identity you use for sign-in serve different purposes. Editing a contact field is not a supported way to move your account to another sign-in email.

If you cannot find your existing work, first confirm you signed in with the same DH Connect email/password account. Do not create duplicate accounts as a troubleshooting shortcut.

Success checklist

The account save is confirmed.

The intended card-level visibility is set.

You know which sign-in identity owns your work.

Tips

Check existing cards after a meaningful contact change.

Keep a record of which DH Connect email/password account you use, without sharing credentials.

Studio basics cannot be edited.

Those shared fields come from Account Info. Update them there, then return to the intended card.

My cards disappeared after signing in.

Check that you used the original DH Connect email/password account and the correct environment/site. Do not assume contact-email edits changed ownership.

Understand announcements, email, and phone permissions

Keep communication channels separate and choose deliberately when a device asks for permission.

Before you start

A compatible browser for optional device notifications.

Distinguish the channels

An in-app announcement or Team Broadcast pop-up appears inside DH Connect. Email arrives at an email address. A phone notification depends on a supported device/browser and an authorized subscription.

Permission for one channel is not permission for all channels. A form submission or contact request is not automatic newsletter consent.

Choose device permission explicitly

If DH Connect offers a phone-notification opt-in, read the explanation before choosing. The browser or device controls the permission prompt; accept only if you want notifications on that device.

A permission on one browser does not necessarily enable notifications on another device or browser profile. Private browsing and device settings can affect support.

Manage a blocked permission in the browser

If you previously blocked notifications, review the site's notification permission in your browser settings. Do not repeatedly click an in-app prompt expecting it to override the browser's decision.

If you no longer want device notifications, use the available unsubscribe control or revoke the site's permission in your browser. Check each device where you opted in.

Review announcements without assuming delivery elsewhere

Read in-app notices where they appear. A scheduled internal announcement is not proof that an email or phone alert was sent.

If you manage team communication, review the audience, channel, content, and approval state separately. Do not present a prepared or scheduled draft as confirmed recipient delivery.

Success checklist

You can distinguish in-app, email, and device channels.

Your device permissions match your preference.

You do not infer delivery from a draft or permission prompt.

Tips

Use your device's instructions for exact permission menus; they differ by browser.

Opt in only on devices you control.

I allowed notifications but did not receive a specific alert.

Check the device/browser permission, subscription, notification settings, and intended channel. Consent enables eligibility, not a guarantee that every announcement creates a phone alert.

Know which AI tools are available

Separate live builder assistance from previews and Coming Soon features, and keep review and publishing in your control.

Before you start

Use only controls currently enabled in your own account.

Check the exact tool name and availability

AI Growth Partner, Ava assistance, Instant URL Builder, and Content Creator are not interchangeable names for one live feature. Read the label and any availability message in your current interface.

A Coming Soon control does not need setup or troubleshooting. You can still build and publish with the standard manual card editor.

Use enabled builder assistance as a draft tool

If Instant URL Builder or Quick Questions is available, provide accurate links or a clear description of your audience, offer, and desired next action. Use public pages the tool can actually read.

Read displayed free-build or usage limits before starting. Do not assume a development owner-preview exemption applies to an ordinary account, or that another AI tool shares the same limits.

Review generated content for accuracy

Check names, promises, claims, contact destinations, media, the Hook question, and every Close. Correct generic wording and remove invented testimonials, urgency, or results.

A failed URL read is not proof that the tool inspected the site. Supply accurate information directly if needed rather than approving unsupported claims.

Keep publication explicit

Generated or conversational edits should be reviewed as private draft work. Follow the actual save/review controls and choose Publish Card explicitly only when you are satisfied.

Do not assume closing an unfinished assistant means it completed a build, saved every change, or published the card. Check the actual state when you return.

Success checklist

You know whether the specific control is available.

Assisted content has been checked against real facts.

You retain the final publishing decision.

Tips

The standard manual builder is a complete alternative.

Do not paste credentials, private customer records, or sensitive information into prompts.

AI Growth Partner is disabled.

A Coming Soon label means the production feature is not currently available to members. It is not an account error.

A builder's free builds are exhausted.

Read the tool's current message and limits. You can continue manually in the standard editor; do not assume the entire free card product is blocked.

AI Growth Partner and Content Creator are marked Coming Soon in the production workspace. Owner/development previews are not a promise of live member access. Builder assistance has its own availability and usage limits.

Troubleshoot common problems safely

Work through sign-in, saving, publishing, media, contact, and data issues without destructive shortcuts.

Before you start

The exact page, action, and visible error if available.

Check the account and page first

Confirm you are on the expected site and signed in with the DH Connect email/password account that owns your work. Finish required Account Setup. Check the Card Name selection or Spotlight variant before assuming content is missing.

A private workspace link asks for sign-in; a published visitor card should be tested using its actual public URL. An owner-only demo is not your live data.

For save or upload errors, pause and read

Wait for any current operation to finish. Read the field-level message and correct the identified input. If a photo upload fails, check file suitability, connection, and storage, then retry manually.

Do not refresh while a save or upload is actively running. Do not assume failed uploads are stored in an offline queue. Avoid repeated clicks that make it harder to tell what succeeded.

For publishing issues, inspect every required stage

Open the intended card in Card Editor, complete Setup and the required content, and review every defined Close. Follow red correction messages, then publish explicitly.

After a confirmed publish, check the exact public link in a private window. A stale social thumbnail is a separate issue from the card's live content.

For media or contact issues, test the destination

Open the provider's own public media link or the intended contact destination. Check whether it requires another app, account, or permission. Reels and TikTok may intentionally use direct-watch cards.

Opening a message draft is not sending it. Check the destination format and finish the native app action yourself when testing.

For empty lists or unexpected counts, check scope

Check filters, reporting period, selected card, live/demo state, and whether a real submission or signup actually happened. Use Refresh or Retry once where available.

Do not create fictional records, duplicate accounts, delete cards, or change sponsor information as a shortcut. A view, a lead submission, and a new member signup are different events.

Prepare a privacy-safe problem description

Record the page, what you selected, what you expected, what happened, the exact visible error, device/browser, and approximate time. Include a redacted screenshot if helpful.

Never include passwords, sign-in codes, session cookies, secret links, private lead contact details, or unredacted account information. Use the actual assistance channel provided by the product owner; this Help Center does not create a support ticket.

Success checklist

You have isolated the failing page and action.

You have checked the relevant account, selection, and published state.

Your issue description contains no private credentials or customer data.

Tips

Do not use deletion or duplicate signups as general troubleshooting tools.

A concise exact error is more useful than 'nothing works'.

I am still stuck.

Use the problem-description checklist and the assistance channel provided to you by the product owner. Include the exact action and redacted evidence; do not guess at a backend fix.

Use DH Connect responsibly and protect private information

Understand public content, private workspace data, consent, and the limits of activity evidence.

Before you start

Review what you intend to publish before sharing.

Separate public and private information

Published cards and active published Member Spotlights are public-facing content. Private drafts, lead information, and internal requests should not be pasted into them.

Review each card's public-contact controls. If you share a social profile or community invitation, assume anyone who can view the published card may use that link.

Keep sign-in and editing private

Use your own DH Connect email/password account and sign out on shared devices. Studio and uploads require authentication; published-card viewing does not grant editing access.

Never share passwords, verification codes, browser cookies, or secrets. Do not ask a prospect for sensitive information through a casual card question.

Respect channel-specific consent

A person asking for one response is not agreeing to an ongoing newsletter. A device notification permission is not email consent. A click is not permission for repeated unsolicited outreach.

Use the consent and unsubscribe controls appropriate to the actual channel. Do not claim DH Connect grants a general legal right to contact someone.

Make accurate claims about activity

A visit, a submitted first name, a button click, a signup, and a delivered message are different things. Do not describe one as another or invent outcomes to make a report look better.

Labels such as verified email do not establish verified identity, income, results, or membership in another program. Labeled demo content remains fictional even if it looks realistic.

Share help requests safely

Redact lead details, request messages, email addresses, phone numbers, and private links from screenshots. Describe a problem with the minimum information needed.

The local checklists in this Help Center store only checklist progress on the current browser when storage is available. They do not modify your account, publish cards, or mark real follow-ups complete.

Success checklist

Published content contains only intended public information.

Contact and notification choices are deliberate.

Activity descriptions stay within what was actually measured.

Tips

Use your own lawful privacy and business practices; this guide is not legal advice.

Before sharing a screenshot, inspect the entire image for private details.

I published a contact method I did not intend to share.

Turn off the relevant card-level visibility, republish, and verify the public card signed out. Previously copied or cached information elsewhere may remain outside the app's control.