Practical instructions for building clearer, less expensive business systems.
These guides come from real implementations, troubleshooting, and internal test projects. Each guide identifies what was tested, when it was verified, what it costs, and where the important limitations are.
No email gate. No invented success claims. Use the instructions yourself or ask RiverdalePro for help when you need it.
Latest guide
Connect Frappe Helpdesk to a Microsoft 365 Shared Mailbox Without Buying Another User License
Use one licensed Microsoft 365 user and a shared support mailbox to create incoming Helpdesk tickets and send customer replies with OAuth. Includes the critical shared-mailbox login setting, GoDaddy tenant notes, troubleshooting, rollback steps, and official sources.
Tested September 3, 2026 Topics: Helpdesk, Microsoft 365, Frappe, Shared Mailboxes, OAuth
Maintain Continuity Across AI-Assisted Projects
A tested operating system for keeping websites, servers, email, CRM, automation, and AI-assisted work understandable across chats and tools. Includes copyable project, handoff, and system-map templates.
Tested September 4, 2026 Topics: AI projects, documentation, operations, security, handoffs
What we document
Helpdesks and customer support
Shared inboxes, ticket routing, service levels, customer records, assignment rules, and support workflows.
Microsoft 365 and business email
Shared mailboxes, authentication, deliverability, forms, routing, permissions, and practical administration.
CRM cleanup and migration
Exports, imports, deduplication, field mapping, system changes, and keeping control of business data.
Automations and integrations
Connections between forms, inboxes, CRMs, reporting tools, and the repetitive office tasks around them.
Websites and lead systems
Trust signals, conversion paths, local pages, structured content, measurement, and maintainable WordPress improvements.
Backups, security, and maintenance
The operational work that keeps useful systems recoverable, current, and understandable.
Our publishing standard
Every RiverdalePro guide should tell you:
- The problem it solves
- Who the guide is for
- The tested environment and verification date
- Exact steps and commands where useful
- Costs, risks, limitations, and rollback options
- Which claims come from official sources
- What remains untested or may change
If a guide becomes outdated, we update its verification date or label it accordingly.
Have a workflow that needs a clearer answer?
Send us the website, email, CRM, or office process that is slowing you down. We will identify the smallest practical improvement worth considering.