Every client renewal an MSP is on the hook for, in one register.

Keep one register of dated records grouped by client, rather than relying on each vendor portal to email whoever set up the account. Every SSL certificate, domain, subscription, warranty and support contract gets an expiry date, an owner and a reminder cadence. In ExpiryEdge the dates come in by spreadsheet import, the API or Zapier; alerts go to Slack or Teams and to the owner at 90, 60, 30 and 7 days; and overdue items escalate. ExpiryEdge does not scan certificates, so feed it from your monitoring or vendor data.

Record each subscription with its term end date, its seat count and the agreement or invoice attached, and assign an owner. Start reminders 90 days out so there is time to reconcile actual users against licensed seats before the renewal or true-up date. Keep the seat count in the record notes and update it at each renewal; the audit trail then shows what was licensed and when. If you are starting from a spreadsheet, the software renewal tracker template gives you a column set to import.

Make each server, firewall, switch or batch of laptops a record with its warranty end date and support contract attached, grouped by client. Set a longer first reminder for hardware, such as 120 days, because replacement quotes and procurement take time. Warranty dates usually come from vendor lookups or your RMM, so push them in by import or API instead of typing them. Owners and escalation make sure someone acts before cover ends.

Filter the register by client and export it as CSV, PDF or XLSX. The report lists every renewal for that client with its expiry date, owner and status, and you can limit it to the next 90 days or the next quarter for a review meeting. Because each record carries a timestamped history, you can also show when the client was notified and when a renewal was completed.

Yes. ExpiryEdge has an API and webhooks, and connects to Zapier. Use the API or Zapier to create or update records when your PSA, RMM, certificate monitoring tool or a vendor export reports a new or renewed date, and use webhooks to send events out when an item is about to expire. A one-off spreadsheet import covers the initial load.

Yes. Reminders can post to a Slack or Microsoft Teams channel at each step of the cadence, 90, 60, 30 and 7 days by default, while the owning technician gets the same reminder by email or SMS. If an item passes its date without a renewal logged, it escalates to a service lead so it does not sit in the channel unread.

No. SSL certificates and domains are tracked as custom items with a date you enter, import or send in by API or Zapier. If you already run a certificate monitoring tool, send its expiry data to ExpiryEdge so the renewal gets an owner, reminders, escalation and a place in the client report. If a certificate has already lapsed, renew or reissue it with the certificate authority first, then record the new expiry date.