Customer Scenarios
Why might the email sending option be unavailable during a trial?
An anonymized customer question, adapted to SugarHR’s published workflow. This is practical guidance, not a verified implementation result.
Check the recipient column and valid addresses before inferring a subscription restriction. Preview the corrected employee mapping and retry the current supported route.
The situation
A team of fewer than 50 preferred email, but its trial spreadsheet did not provide usable email information.
Why this condition changes the workflow
A disabled option can originate in the data supplied to the workflow. Keep the diagnosis specific: missing or unrecognized email fields are different from an account lacking a paid entitlement.
A practical sequence for this situation
1. Investigate the original email record. Validate the address and batch, review delivery and opening information and check spam with the recipient. Preserve error details and timing if unresolved; avoid creating another indistinguishable payroll batch.
2. Isolate a recognizable data structure. Keep the employee header and data separate from summary and approval regions. Test one or two rows that preserve the genuine columns, then compare the recognized fields and important amounts with the source.
3. Correct the identified record. Find the affected employee and original batch, check its acknowledgment state and use the supported correction process. Preview the approved replacement and preserve the link between old and revised information.
4. Choose a representative pilot. Use a small anonymized or simulated sample reflecting the real layout and employee conditions. Confirm current trial limits and record observations for receipt, review, acknowledgment, correction and retrieval before expanding.
What a useful test should demonstrate
Record the tested recipient route, the account and batch, and the employee’s observed access result. Distinguish an available administrator control from a usable employee journey. If the intended route cannot be demonstrated, or a failed route has merely been bypassed, keep that condition open rather than mark the whole delivery problem solved.
Questions to resolve in this context
How should an existing Excel file be prepared?
Use approved figures and a recognizable header and employee-data region. Check identifiers, periods and recipient addresses, keeping totals and sign-off areas distinguishable. A small structural sample helps diagnose parsing without unnecessarily rebuilding a workbook that supports the existing calculation process. Read the general explanation.
How should a trial be separated from live payroll?
Begin with simulated or anonymized, structurally representative data and confirm current trial conditions. Test receipt, acknowledgment, correction and retrieval. A demonstration is learning material; before going live, recheck the organization's approved amounts, recipients and period rather than reusing arbitrary sample values. Read the general explanation.
Related guidance
Test the conditions that matter to your team
Use a sample or anonymized approved file to check the specific conditions described here. Confirm any unverified account, channel or record requirement before a live send. Start Your Free 1-Month Trial.
Published by SugarHR Help Center. How we review guidance.
Start Your Free 1-Month Trial