# Orlando G.

Orlando G. shares practical HubSpot workflows for sales and customer support, including scheduling, discovery-call playbooks, ticket routing, customer feedback, and deal reporting.

- Profile: https://b2binfluencer.marketing/creators/orlando-g/
- LinkedIn: https://www.linkedin.com/in/orlandogonzalez77
- LinkedIn followers: 19,441
- Topics: artificial-intelligence, sales, revenue-operations, sales-enablement, pipeline-management
- Based on 11 dated posts, latest 2026-10-08

## Summary

Orlando G. is most useful for practical HubSpot workflow tutorials covering sales and support processes with concrete CRM steps.

- Best for: B2B SaaS selling HubSpot sales and customer support automation to ops leaders.
- Not for: Consumer-facing sponsored lifestyle campaigns needing rate cards, guaranteed impressions, and demographics.
- Check first: Before contacting, confirm commercial terms, video depth, audience demographics, and performance data.

### Takeaways

- A self-scheduling meeting page logs the booking to the contact record.
- A shared support inbox routes into a HubSpot ticket queue.
- A closed support ticket can trigger a CSAT survey.

## Main ideas

- **The real failures are quiet handoffs, not missing tools**: The posts rarely frame the problem as a missing feature. Instead, work stalls as it passes between people or systems, often without anyone noticing: a prospect who agreed to talk goes silent in a scheduling thread; one person effectively becomes the support queue; or a ticket is marked closed before the customer confirms the fix. The reasoning is consistent: these gaps stay invisible because nothing prompts anyone to check. The fix is to make the handoff explicit and visible, rather than add another tool.
- **Let AI take the first pass, keep a person on the decision**: AI appears in two posts, drafting or sorting rather than deciding in both. For the discovery playbook, HubSpot Breeze produced several framework options; Orlando G. chose the best one and corrected a setting Breeze had defaulted incorrectly. In support, AI makes a first pass against the knowledge base, then hands the conversation to a human with an owner assigned. The pattern: AI broadens the starting options and handles routine sorting, while a person makes the judgment call and replies to the customer.
- **Record the reason while it is still known**: A recurring argument is that reports show what happened in a pipeline or support queue, but not why—and that the reason is available only in the moment. The proposed remedy is a required input at the point of closure. Judging performance by gut feel or stage movement alone is the default failure this guardrail is meant to prevent.
- **Keep the build inside HubSpot and write the result to the record**: None of the described setups use an outside tool. Scheduling, ticket routing, surveys, deal fields, and playbooks all use HubSpot's own features, and the stated payoff is usually an automatic record update. For anyone evaluating the work, that means each change is small and testable within a stack they may already run, rather than requiring a migration or integration project.
- **Prefer one small, testable change over a system overhaul**: Each post isolates one point of failure and proposes one change: a required field, survey trigger, scheduling page, ticket queue, or AI-drafted framework. The priority is a change a team can copy and test quickly, not a reporting overhaul or broad process redesign. Out-of-the-box behavior may need adjustment: the discovery-playbook post says HubSpot usually defaults the answer type incorrectly. Check that setting before using the playbook.

## Work to read

- [Build a self-scheduling meeting page inside HubSpot](https://www.linkedin.com/posts/orlandogonzalez77_revenueoperations-revops-hubspot-activity-7510464421391958017-vODi)
- [Route a shared support inbox into a HubSpot ticket queue](https://www.linkedin.com/posts/orlandogonzalez77_revenueoperations-revops-hubspot-activity-7511840812192935936-myJo)
- [Fire a CSAT survey when a support ticket closes](https://www.linkedin.com/posts/orlandogonzalez77_revenueoperations-revops-hubspot-activity-7513718958831583232-Lqim)
- [Make the closed lost reason a mandatory field in HubSpot](https://www.linkedin.com/posts/orlandogonzalez77_revenueoperations-revops-hubspot-activity-7508672976503054336-Dpsi)
- [Use HubSpot Breeze to draft a discovery-call playbook](https://www.linkedin.com/posts/orlandogonzalez77_revenueoperations-revops-hubspot-activity-7509383123659325440-ZmTZ)

## Brand relationships

- **HubSpot** (mention)

## Partnerships

The five posts are walkthroughs of HubSpot builds: an in-CRM scheduling page, a discovery-call playbook drafted with HubSpot Breeze, routing a shared support inbox into a ticket queue, a CSAT survey triggered when a ticket closes, and a mandatory closed-lost reason on deals. None mentions a sponsorship, named partner, rate, package, or commercial inquiry route. The posts also show no official media kit, rate card, or partnership page. For a paid engagement, ask Orlando G. directly to confirm deliverables, pricing, exclusivity, review and approval steps, lead time, and how the work would be scoped, staffed, and measured. The only official route visible in the posts is the LinkedIn profile, a general contact channel rather than a documented partnership route. The posts show implementation work with HubSpot tooling but do not say whether it was sponsored.

## Alternatives

- Daniel Buckle: Choose Buckle when the campaign is about recovering demand the buyer already paid for, rather than building a new HubSpot workflow. The two posts start with the closed-lost deal: a prospect loves the solution but has no budget, gets marked closed lost, disappears into CRM history, and is forgotten by the time a new budget year arrives. Buckle separates reasons teams normally collapse into one bucket — no budget now, focused elsewhere, revisit next quarter, went with a competitor — and argues that each should trigger a different next step and follow-up timing. A brand selling a re-engagement, winback, or lifecycle-signal tool addresses the same buyer problem. Buckle's second post extends the idea to retention: onboarding slowdown, falling product usage, rising support contacts, and quiet renewals are signals that should shape what happens next rather than sit in separate systems. Use Buckle when the campaign needs strategy and signal design for deals or customers already in the HubSpot stack.
- Chris Tveter: Choose Tveter when the campaign is about AI assistants and new HubSpot features changing sales reps' day-to-day work, rather than a process a team builds once. The posts cover HubSpot's Sales Plugin for Claude, with eight named skills mapped to specific rep moments: call prep before a meeting, a morning prioritisation brief, logging a call in plain language with the stage advancing and follow-up tasks created, drafting the recap email from deal history, a pipeline pulse before a weekly review, contact lookup, and CSV import with deduplication. Tveter picks two to start with and explains why. The second post covers HubSpot Deal Progression in public beta: transcript-based CRM update suggestions, next-best-action, drafted follow-up, a Catch-Up tab, methodology configuration for MEDDIC, BANT, or SPICED, stamped buyer portals, and a re-engage prompt after fourteen days of silence. Tveter also flags rollout details that determine whether adoption works: recording has to be on, admin steps activate methodology and deal plans separately, and a default layout renames the Overview tab. Brands with an AI layer in front of a CRM, or campaigns focused on an enablement rollout to reps, address that same decision with greater specificity here than in Orlando G.'s native-automation builds.
- Anurika Okoyenta: Choose Okoyenta when the decision is about the people and conversations around a process, not the automation that runs it. The posts focus on customer success practice. One argues that the post-sale conversation matters more than the feature tour: a customer success manager should ask why the customer bought, understand the challenges and goals shared before the sale, and validate rather than assume. The same product can serve different outcomes for different customers, and the sales handoff is where that context gets lost or preserved. The other post teaches CSAT for a customer success manager — what the score tracks, how it surfaces churn risk and advocates, why it measures whether customers are getting value, and how the percentage is calculated from the top two scores on a five-point scale. Brands focused on the human side of onboarding, handoff, or score interpretation — or on convincing a customer success audience rather than an ops audience — reach that reader more directly here than through an automation walkthrough.

---
AI-assisted summary of public posts. Audience demographics are not available. Engagement appears only where we checked recent posts. Method: https://b2binfluencer.marketing/methodology/