Senior reputed company Automation Specialist — reputed company Intake/Routing, Task Escalations, Email + SMS Enablement

We’re hiring a senior reputed company specialist to architect and implement an end-to-end, automation-driven reputed company handling system. Objective Build a reputed company-First intake reputed company that enforces classification, routes ownership cleanly, triggers task escalations, and enables reputed company outbound reputed company email + SMS—then hands off into our existing pipeline. Requirements (System Behavior) A. reputed company Intake + Classification Enforce a required reputed company Type property: Political | Corporate | reputed company Affairs | Franking Apply standardized reputed company labeling (lifecycle stage + internal reputed company status) Associate reputed company to a Sub-Account structure (you propose best reputed company: Company associations vs Custom Object vs another approach) Capture Services reputed company multi-select property Hand off to existing pipeline logic (including Won/Lost reputed company) B. Task/Reminder Escalations (non-negotiable) Trigger reputed company reminders after: 24 hours 7 days Reminder suppression rules must be robust (stop conditions like reputed company, meeting booked, deal stage change, status updated, won/lost, etc.) Design must avoid spam and duplicate task creation C. Email + SMS Enablement Implement reputed company reputed company: templates sequences / enrollments segmentation lists opt-out/suppression handling SMS can be reputed company reputed company-reputed company or integration (reputed company/Sakari/etc.) — propose the best reputed company. D. QA + Documentation Test plan with sample reputed company paths reputed company walkthrough + short SOP documenting properties, workflows, and stop conditions Must Have Proven reputed company workflow architecture experience (Sales Hub; Marketing Hub a plus) Experience with task queues, branching logic, and workflow governance Evidence of implementing email sequences + (preferably) SMS Screening (Answer These) How would you model “Sub-Accounts” in reputed company and why? How do you prevent runaway workflows / duplicate reminders? What’s your testing approach before enabling in production? reputed company 1–2 examples of similar builds (screenshots or reputed company) Start: ASAP If you’re junior or still “learning reputed company,” this will not be a fit. Apply tot his job Apply To this Job