Happy Days RV Park Support
Hi, how can we help you?
Most popular articles
View all articlesTrigger
Integration Required — connect verified workflow trigger(s) or paste the confirmed trigger here.
Primary Actions
Integration Required — add the confirmed action list in execution order.
Conditions / Branches
Integration Required — add condition logic and branches.
Tags / Stage Updates
Integration Required — add tags added/removed and any pipeline stage changes.
Notifications
Integration Required — list recipients and notification channels.
Next Steps
Use the Pipeline Flow tool for a visual walkthrough. Add stage-specific notes once verified.
Testing checklist (local)
Note: checklist state is saved locally in the staff member’s browser (no shared database). For shared audit history, an integration is required.
Trigger
Integration Required — confirm form submission trigger mapping.
Primary Actions
Integration Required — add the verified actions (tags, stage change, notifications).
Conditions / Branches
Integration Required — add background-check branching logic by accommodation type.
Tags / Stage Updates
Integration Required — list approval/denial tags and stage transitions once confirmed.
Notifications
Integration Required — add recipients and message templates.
Next Steps
Link to Agreements and Deposits once triggers/actions are verified.
Testing checklist (local)
Note: checklist state is saved locally in the staff member’s browser (no shared database). For shared audit history, an integration is required.
Trigger
Integration Required — confirm which event(s) select and send the correct template.
Primary Actions
Integration Required — add the exact template IDs and delivery steps.
Conditions / Branches
Integration Required — add logic for accommodation type and electrical service selection.
Safeguards
Integration Required — prevent wrong template selection and duplicate sends.
Notifications
Integration Required — list recipients and exceptions handling.
Next Steps
Connect to “Agreement Signed — Payment & Next Steps” once verified.
Testing checklist (local)
Note: checklist state is saved locally in the staff member’s browser (no shared database). For shared audit history, an integration is required.
Purpose
Reference-only module. Integration Required to pull verified, authorized rates from a controlled source.
Billing Safety
Never treat deposits as rent. Verify invoice vs subscription behaviors in test mode.
Dependencies
Integration Required — connect to approved pricing controls (GHL/Stripe configuration).
Next Steps
Use the Late-Fee Calculator tool for training calculations (simulation only).
Testing checklist (local)
Note: checklist state is saved locally in the staff member’s browser (no shared database). For shared audit history, an integration is required.
Training Tool
The Late-Fee Calculator below is a simulation only. It does not charge residents and does not update Stripe or GHL.
Automation Note
If the current workflow cannot reliably compute + apply fees, an integration is required (custom API/app) before marking “Active — Verified.”
Safeguards
Exclude paid/voided/canceled invoices; prevent duplicates; stop accrual once paid.
Next Steps
Use the checklist to document what was tested and any limitations.
Testing checklist (local)
Note: checklist state is saved locally in the staff member’s browser (no shared database). For shared audit history, an integration is required.
Clarification
This panel is documentation-only until integrations are verified. It does not sync invoices/subscriptions by itself.
Risks
Duplicate charges, mismatched invoice vs subscription amounts, and deposit-vs-rent confusion.
Dependencies
Integration Required — confirm Stripe subscription config + GHL invoice logic + webhook behavior.
Next Steps
Use checklists to validate in test mode before marking verified.
Testing checklist (local)
Note: checklist state is saved locally in the staff member’s browser (no shared database). For shared audit history, an integration is required.
Purpose
Document scheduled vs confirmed move-in handling. Integration Required to pull verified field mappings.
Safeguards
Do not mark Active Tenant until actual move-in is confirmed (manual or verified automation).
Site Status Tie-in
Use Site Availability Simulator for training the correct status transitions.
Next Steps
Connect to billing verification and site inventory synchronization once verified.
Testing checklist (local)
Note: checklist state is saved locally in the staff member’s browser (no shared database). For shared audit history, an integration is required.
Requirement
Integration Required — accurate site inventory synchronization normally requires controlled records + validation.
Safety
Never release an occupied site based on a cleared field alone. Confirm vacancy before marking available.
Training
Use the Site Availability Simulator for safe staff training using sample records only.
Next Steps
Define and verify the authoritative inventory source and mapping before automation.
Testing checklist (local)
Note: checklist state is saved locally in the staff member’s browser (no shared database). For shared audit history, an integration is required.
Status
Manual Process until subscription cancellation integration is verified + tested.
Safety
Cancel the correct subscription; record outcome/effective date; release site only after vacancy confirmed.
Dependencies
Integration Required for automated Stripe cancellation (API/webhooks) with permission checks.
Next Steps
Use Site Availability Simulator to train safe site release rules.
Testing checklist (local)
Note: checklist state is saved locally in the staff member’s browser (no shared database). For shared audit history, an integration is required.
Responsibility Map
Reference panel. Integration Required to link responsibilities to verified workflow ownership.
Notifications
Integration Required — document the configured recipients per workflow.
Next Steps
Cross-link each workflow to “Responsible Staff Member” once verified.
Training
Use simulations for step-by-step training with sample data only.
Testing checklist (local)
Note: checklist state is saved locally in the staff member’s browser (no shared database). For shared audit history, an integration is required.
Trigger
Integration Required — confirm inbound call/missed-call triggers and safeguards.
Actions
Integration Required — add callback task rules and messaging steps.
Duplicate Prevention
Integration Required — confirm rules to avoid duplicate tasks and repeated messages.
Next Steps
Cross-link to Application Form workflow once verified.
Testing checklist (local)
Note: checklist state is saved locally in the staff member’s browser (no shared database). For shared audit history, an integration is required.
Tooling
Use checklists + simulations to document tests without touching live records.
Integration
Integration Required for verified status, shared progress, and audit history.
Errors
Capture: trigger conditions, timing, duplicate prevention, message delivery, billing outcomes, and inventory updates.
Next Steps
Standardize a test plan and mark workflows verified only after repeatable success.
Testing checklist (local)
Note: checklist state is saved locally in the staff member’s browser (no shared database). For shared audit history, an integration is required.