Frequently asked questions

The core DH Connect card tool is free. Publishing a standard card is not a purchase or a requirement to join another program. Optional tools can have their own availability and usage limits; read the actual tool's message rather than assuming unlimited AI generation.

Open https://dhconnect.io/sign-up and create your DH Connect account using Email + Password. Return at https://dhconnect.io/sign-in with the same sign-in email and password. If invited, begin with your invitation link and review the displayed sponsor before completing Account Setup.

Open https://dhconnect.io/sign-in and select Forgot password. Follow the verification and reset steps for your sign-in email. Your Account Info contact email is a separate field. Never share a password or verification code.

Account Setup needs to be completed before private workspace use. Review the required details and sponsor information, then submit. Creating another account is not a solution for an incomplete setup.

Complete Account Setup, create one simple card in Studio, work through Setup, Front Door, The Hook, and The Close, then publish and test the public link signed out. You do not need to learn every team tool before sharing a card.

No. The standard manual card editor is a complete way to build and publish. Use assistance only if the specific control is enabled and its limits and draft behavior make sense for your task.

The workspace adapts to smaller screens, where navigation may appear as an icon rail. Use the icons' labels or titles to identify destinations. Test the finished visitor card on a phone as well as in the editor.

Those production workspace controls are not currently available as live member features. A development or owner preview does not mean they are released to everyone. You do not need to configure them to use the standard card builder.

No. The tools have distinct purposes, availability, and usage limits. Read the exact control name and current status. An enabled builder assistant is not proof that the separate AI Growth Partner workspace is released.

Treat assistance as draft work and review its results. Publication requires your explicit Publish Card action. Check the actual saved state when returning to unfinished work; closing an assistant is not proof that it finished or published.

Yes. Use an article's print action and your browser's Save as PDF option, or download the complete written handbook from the Help Center. Browser print menus vary. The handbook is a snapshot; check the online Help Center for later updates.

Include the page, selected card or feature, exact action, expected and actual result, visible error, device/browser, and approximate time. Redact private information. Do not include passwords, codes, cookies, secrets, or private lead details. This Help Center does not submit support tickets.

Standard Studio currently provides five card slots. When all five are in use, Create New Card is unavailable. Review Card Vault carefully before deleting an existing card to make space.

No. Card Name is an internal organizer. The public handle determines the card's public URL, and visitor-facing headings are separate content. Renaming a card does not automatically change its public link.

Use the Card Name selector in Studio and check the selected card before editing or publishing. Wait for saves and uploads to finish before switching.

Use the card's naming control in Card Vault, enter a descriptive internal name, and choose Save Name. This does not rename a reusable media source or reserve a different public handle.

Use Delete inside Card Vault for the specific card and read the confirmation. Deletion is not a temporary pause. Check shared links and preserve important content before confirming; cancel if you are unsure.

No. Signed-in draft autosave keeps unfinished work private. Continue validates or completes the relevant stage; Publish Card explicitly updates the public version. These are separate actions.

Yes, private draft saving supports unfinished signed-in work. Wait for the save status and current uploads to finish, and resolve any error before leaving. Do not assume a failed save or upload completed in the background.

Setup configures the selected card. Front Door introduces the offer. The Hook asks a useful question with answer choices. The Close gives each defined answer a relevant message and next action.

Setup is private configuration. Visitor previews belong on the card-content steps such as Front Door, The Hook, and The Close.

Shared basics come from Account Info and may be read-only in Studio. Correct them in Account Info, save, then return to the intended card and review whether its public version needs republishing.

Ask one easy question about what would help the visitor now. Use distinct, truthful answer choices that lead to useful next steps. Avoid internal tag labels, sensitive questions, or choices that all mean the same thing.

Different answers represent different visitor needs. Each defined choice has its own message, media, and next action. Review every choice; editing one ending does not automatically update the others.

Check whether the corresponding Hook choice is defined. Only the choices you actually define should appear as choice-specific Close editors. Revisit The Close after changing your answers.

Use 1–40 lowercase letters, digits, or hyphens, beginning with a letter or digit. System paths are reserved and another card may already own a handle. The builder's availability result is authoritative.

It may be reserved or already owned. Pick another clear variation. An internal card name does not reserve a public handle, and creating a new card must not silently replace an existing public card.

Select a card and open it in Card Editor rather than Card Vault. Wait for saves or uploads to finish, then resolve required fields or validation messages. Read the visible reason instead of repeatedly clicking.

A field or stage needs correction. Read the inline instruction and fix that specific value; the builder may move you to the affected section. A draft can exist without being complete enough to publish.

Yes. Review the edits and choose Publish Card to apply the intended update to the public version. Then check the exact public URL in a fresh private window.

Confirm the selected card, a successful republish, and the exact URL you opened. Test signed out. If only a social thumbnail is old, that can be external preview caching rather than an outdated card.

Use the published card URL provided by the app. Do not share Studio or Pipeline addresses, which are private. Use a referral invitation when your goal is to invite someone to create an DH Connect account.

dhconnect.io is the main marketing and dashboard hub. dhconnect.me is the clean-link personal card runtime. Copy the app-provided URL for your task instead of reconstructing one by hand.

Check whether you shared a private workspace URL instead of the published card link. Published visitor cards should be tested independently of your signed-in editing session.

External apps can cache link titles and images. Confirm the card itself is updated, use the current share option after publishing, and distinguish the cached preview from the actual destination page.

The app optimizes photo uploads; the optimized image must be 8 MB or smaller. Check the account storage indicator too. A smaller, clear source image can help when an upload fails.

Check the connection, image suitability, and available storage, then retry manually. Do not assume a failed file is queued offline or will upload automatically later.

Yes. Use My Media and the available media picker, give photos recognizable names, and review the selected image in the correct stage. Do not assume selecting it automatically publishes the card.

Confirm you selected the right card and published after changing the image. Test signed out and note whether the failing image is on The Hook or a specific Close. Use the troubleshooting guide if the published image still fails.

The carousel batch picker supports up to six images at once. Uploads fill empty slides without replacing existing photos. Review the slide order, aspect ratio, and any empty slides before publishing.

No. Selecting a reusable carousel copies content into the card. Edit the reusable source separately if you intend to change it, and update other card copies explicitly as needed.

No. A photo or carousel can communicate your message. Choose the format that genuinely helps the visitor, and keep important information understandable without playback.

The direct video-upload flow is currently disabled. Use the available link-based media controls with an existing supported public watch link, or use a photo/carousel instead.

Direct-watch cards are intentional for Meta Reels and TikTok because mobile iframe playback can be unreliable. Test that the link opens the intended media; the provider controls its own access requirements.

Your provider login may let you see content that is not publicly watchable or embeddable. Test the watch page signed out and check its permissions, restrictions, and availability at the hosting provider.

You may not have genuine submissions yet. A card visit is not automatically a first-name submission or captured lead. Check the selected card, available filters, live/demo state, and refresh result.

No. It is self-reported context. It does not establish verified identity, complete contact information, membership, buying intent, or a completed conversation.

No. A click or app handoff may open a destination or prepare text. The visitor still needs to send the message, and that event alone is not confirmed delivery or a completed conversation.

No. Pipeline concerns genuine visitor submissions and follow-up. A team member requires an actual attributed signup and sponsor relationship. Views, clicks, and names are not team enrollment.

Historical records may not contain the same breakdown as newer button tracking. Retain the totals within their original scope; do not infer exact past actions that were not recorded.

They serve different scopes: prospects in Pipeline versus members in Team Command. Use the correct workspace and authorized options. A matching tag name does not make them the same relationship.

The Pipeline mapping is tied to the matching CTA click. The Team mapping requires a new attributed signup under its conditions. Choosing an answer alone is not sufficient for a Team tag, and tags do not change sponsorship.

External activity should not be assumed to clear your own reminder. If the reminder offers Done, use it when the actual task is complete. Review the saved state rather than expecting an unrelated automation to resolve it.

Open Member Spotlight and use its own tabs. Member Card Studio belongs there, not in the standard Studio card editor.

Active published Member Spotlights may appear on public surfaces. Drafts and inactive variants are distinct. Publish only information you intend to be public and do not include private lead details.

In this member context it means verified email. It is not a claim of independently verified identity, business results, income, or membership in another program.

No. A referral link invites someone to join DH Connect through you. A published card link opens your visitor-facing card. Use the exact link provided for your goal.

Opening a link does not complete a new attributed signup. They may not have finished setup or may already have an account. Do not create duplicate accounts or assume a click establishes sponsorship.

No. Permanent referral lineage is separate from tags and card choices. Do not promise a sponsorship change through those controls.

The selected reporting period and tag scope affect which activity is summarized. Compare like-for-like periods and do not interpret app activity as proof of sales or business outcomes.

No. Owner-only Demo View uses labeled fictional presentation data. It must not be treated as real leads, referrals, awards, messages, or deliveries.

No. They use private recipient-owned request forms. Review the supplied request and available next actions; do not expect live chat or infer confirmed receipt from submission alone.

Inbox is for internal requests. Pipeline is the destination for genuine visitor submissions and lead follow-up. They are intentionally different areas.

Not automatically. Tagged Team Broadcast pop-ups and phone-notification campaigns are independent channels with their own audience, approval, and consent requirements.

The selected card's Make E-mail public and Make phone public controls override the general Account Info preference. Review them separately and republish to change the live card.

Check the branded header's AccessInfo dropdown. Published email, phone, social profiles, and community links live there rather than being repeated throughout the body.

No. Account Info contact details and your Email + Password sign-in identity are separate settings. Editing a contact email does not transfer account ownership. Return with the same sign-in email to find your existing work.

The device/browser may download or open a contact file containing published contact methods. It is not a guarantee the contact was saved in the address book. Review the file or contact prompt and complete the device's action.

No. A bounded request or first-name submission is not blanket marketing consent. Use the appropriate channel-specific opt-in and respect unsubscribe preferences and applicable rules.

Use the available in-app opt-in and your browser/device's site-permission settings. If you previously blocked permission, change it in the browser. To stop, use available unsubscribe controls or revoke the site permission on each relevant device.

Permission enables a channel; it does not mean every notice produces a device alert. Check the intended channel, subscription, device/browser permissions, and device notification settings.

No. Visibility and deletion are different. Turn off the relevant card's public setting and republish to hide it there. Previously copied or externally cached information is outside that setting's control.

No. They are learning aids stored on the current browser when local storage is available. They do not publish cards, complete real reminders, change team records, or sync across accounts and devices.