Peru

Customer Service Representative

Salary: unknownRemoteMidCustomer success and support

ZendeskFreshdeskSalesforceCustomer serviceLive chatDe-escalationCustomer successTicketing systemsPhone supportNPS/CSAT

Original posting ↗Apply ↗Company job board ↗

Customer Service Representative is an open role at Pavago, a company in consulting, agencies and business services. This is a remote position, and the posting gives Peru as the location. We classify it as a mid-level role in customer success and support. Candidates need 1+ year of experience. English is required. There are 187 open positions from Pavago on this site, 25 of them in IT and engineering.

Posted 13 days ago · Last checked 2026-10-27

About Pavago

Consulting, agencies and business services Non-tech company with an IT team 187 open positions, 13% in IT and engineering. Most open roles: Sales (84), Marketing and communications (59), Operations and admin (43).

All open jobs at Pavago →

Similar jobs

AI Technical Support Specialist | Based in LATAMHostinger · Buenos Aires, Argentina | Peru | Ecuador | ColombiaRemote Associate Field Manager - Call Center (Fixed Term Contract)GiveDirectly · KituiRemote Account Support RepresentativeBillionToOne · South CarolinaUSD 129.0K / year Scaled Support SpecialistOpenRouter · Remote (US)USD 115K–140K / year Customer Support Training & Enablement SpecialistMudflap · Remote | Austin, TX | Palo Alto, CAUSD 67K–85K / year RVP, Client Services - Eastern USStackAdapt · Connecticut; Florida; Georgia; Maryland; Massachusetts; New Jersey; New York; Pennsylvania; United States; VirginiaRemote Customer Service Officer (030-1450)Hunt St · PhilippinesUSD 800–1,000 / month Customer Onboarding and Support SpecialistVirtual Staff 365 · PhilippinesRemote

673 open remote customer success and support jobs All open jobs at Pavago →

Workplace	Remote
Seniority	Mid
Role	Customer success and support
Countries	Peru
Key facts	Tools: Zendesk, Freshdesk, Salesforce · Experience: 1+ year · Languages: English · Remote

The full description is on the original posting. Labels are set automatically and can be wrong. About the data