Fee petition mechanics · Updated July 2026
California automated calling ADAD attorney fee petition mechanics: date of unlawful automated call in cloud communications platform outbound call log as primary Welch anchor, Pub. Util. Code § 2875 attorney fees — $500 per violation plus mandatory attorney fees; Ketchum/Dague analysis when TCPA concurrent; THE ONLY page where primary Welch anchor is in a cloud communications platform's own outbound call log; DISTINCT from CIPA § 637.2 and CalECPA § 1546.4
California automatic dialing-announcing device (ADAD) restriction enforcement (Pub. Util. Code §§ 2871–2878 — enacted 1985, most recently amended 1997; § 2871: 'automatic dialing-announcing device' means any automatic telephone dialing system or device that incorporates a storage capability of numbers to be called or a random number generator capable of producing numbers to be called, and when connected to a telephone line, will deliver a prerecorded message; § 2872: no person operating an ADAD shall use that device to call any residential telephone subscriber unless that person has the prior consent of the person being called or has an established business relationship with that person; § 2872 also prohibits use of ADADs to place calls before 9:00 a.m. or after 9:00 p.m.; § 2874: a caller using an ADAD must identify the name and telephone number of the entity transmitting the message within the first 30 seconds of the call — failure to identify is an independent § 2875 violation; § 2875: 'any person who is injured by a violation of this article may bring a civil action for actual damages or five hundred dollars ($500), whichever is greater, for each violation, together with costs of suit and reasonable attorney's fees'; the ONLY fee-petition-mechanics page where the primary Welch anchor is in a CLOUD COMMUNICATIONS PLATFORM'S OWN OUTBOUND CALL LOG CALENDAR DATE [Twilio Programmable Voice, Five9 CRM Dialer, NICE CXone ACD, Genesys Cloud CX, Avaya OneCloud CCaaS, Amazon Connect, Cisco Webex Contact Center, Nuance Conversational AI, LivePerson, Vonage Contact Center — each records the outbound call datetime, destination telephone number, caller ID (CNAM/ANI), call duration, and message delivery status in the platform's own institutional call log calendar entirely outside plaintiff attorney's scheduling control]; the federal Telephone Consumer Protection Act (TCPA) 47 U.S.C. § 227 is a concurrent federal cause of action: § 227(b)(1)(B) prohibits automated calls or prerecorded messages to residential telephone lines without prior express consent; § 227(b)(3) provides $500 per violation (trebled for willful violations) — federal TCPA provides its own damage minimum without a Ketchum multiplier; California § 2875 attorney fees are subject to pure Ketchum analysis; Hensley task-level segregation required to identify California-only § 2875 hours vs. federal TCPA hours; DISTINCT from Pen. Code § 637.2 CIPA [§ 637.2 requires recording of a telephone call without all-party consent; § 2875 covers automated dialing to residential lines without prior consent — CIPA requires recording; § 2875 requires only automated dialing; a robocall that delivers a prerecorded message without recording the recipient's response does not violate CIPA but may violate § 2875]; DISTINCT from Pen. Code § 1546.4 CalECPA [§ 1546.4 covers government agency requests for electronic device information; § 2875 covers private commercial automated calling to residential subscribers]; Ketchum v. Moses 24 Cal.4th 1122 (2001); PLCM Group Inc. v. Drexler 22 Cal.4th 1084 (2000); Hensley v. Eckerhart 461 U.S. 424 (1983) lodestar from DATE OF UNLAWFUL AUTOMATED CALL; Missouri v. Jenkins 491 U.S. 274 (1989) fees-on-fees) — solos billing hourly on attorney fee recovery — in actions where the primary Welch temporal anchor is the DATE OF UNLAWFUL AUTOMATED CALL (in the TELECOMMUNICATIONS PLATFORM'S OWN OUTBOUND CALL LOG: Twilio/Five9/NICE CXone/Genesys Cloud/Avaya OneCloud/Amazon Connect — call datetime, destination number, caller ID, call duration, message delivery status entirely outside plaintiff attorney's scheduling control; § 2875 $500/violation plus mandatory attorney fees; CPUC complaint calendar as second institutional calendar; FCC TCPA enforcement calendar as third; Ketchum/Dague analysis required when TCPA § 227 concurrent; DISTINCT from CIPA § 637.2 [recording]; DISTINCT from CalECPA § 1546.4 [government surveillance]) — generate three billing gaps driven by § 2871 ADAD definition and prior consent analysis advisory calls, the concurrent telecommunications platform call log calendar and CPUC complaint calendar and FCC TCPA enforcement calendar advisory calls on external institutional calendars entirely outside attorney control, and the § 2875 attorney fee petition and Ketchum/Dague analysis advisory calls: § 2871 ADAD definition and prior consent analysis advisory calls (7 clients × 2 calls × 42 min × 55% untracked ≈ 5.39 hrs = $1,617–$2,695/year at $300–$500/hr), telecommunications platform call log calendar advisory and CPUC complaint calendar advisory and FCC TCPA enforcement calendar advisory (6 clients × 3 calls × 44 min × 55% ≈ 7.26 hrs = $2,178–$3,630/year), and § 2875 attorney fee petition and Ketchum/Dague analysis advisory calls (5 clients × 2 calls × 44 min × 55% ≈ 4.03 hrs = $1,210–$2,017/year). For a solo California § 2875 ADAD automated calling practice, the annual billing gap from advisory call underlogging is $5,005–$8,342.
TL;DR
ClaimHour captures every § 2871 ADAD definition and prior consent analysis advisory call that starts the § 2875 fee documentation period from the DATE OF UNLAWFUL AUTOMATED CALL (in the TELECOMMUNICATIONS PLATFORM'S OWN OUTBOUND CALL LOG: Twilio/Five9/NICE CXone/Genesys Cloud/Avaya OneCloud/Amazon Connect — call datetime, destination number, caller ID, call duration, message delivery status entirely outside plaintiff attorney's scheduling control; § 2875 $500/violation plus mandatory attorney fees; ONLY page where primary Welch anchor is in a cloud communications platform outbound call log; Ketchum/Dague analysis when TCPA § 227 concurrent; DISTINCT from CIPA § 637.2 [recording requirement]; DISTINCT from CalECPA § 1546.4 [government agency surveillance]), every concurrent telecommunications platform call log advisory and CPUC complaint calendar advisory and FCC TCPA enforcement calendar advisory call on external institutional calendars entirely outside attorney control, and every § 2875 attorney fee petition and Ketchum/Dague analysis advisory call — passively, no timer, no audio, no call contents. $29–$59/mo. No PMS required.
§ 2871 ADAD definition and prior consent analysis: calls on the telecommunications platform's outbound call log
The DATE OF UNLAWFUL AUTOMATED CALL is the primary Welch temporal anchor for § 2875 California ADAD attorney fee billing. This date is in the TELECOMMUNICATIONS PLATFORM'S OWN OUTBOUND CALL LOG CALENDAR DATE. The Hensley lodestar starts from this date for five reasons: (1) Twilio Programmable Voice, Five9 CRM Dialer, NICE CXone ACD, Genesys Cloud CX, Avaya OneCloud CCaaS, Amazon Connect, and Cisco Webex Contact Center each record the outbound call datetime, destination telephone number, caller ID (CNAM name and ANI telephone number), call duration, message delivery status, and agent or automated flow identifier in the platform's own institutional call log calendar entirely outside plaintiff attorney's scheduling control; (2) the call log is corroborated by the defendant's own dialer campaign records: most cloud contact center platforms maintain campaign records (Five9 campaign management, NICE CXone ACD campaign scheduler, Genesys Cloud outbound campaign manager) that record the campaign start date, contact list upload date, and outbound call authorization date — all on the platform's institutional campaign management calendar; (3) the predictive dialer's abandoned call records are in the platform's call log: predictive dialers (a subset of ADADs) generate abandoned calls when the dialer connects before an agent is available — these abandoned calls are logged in the platform's call log with the same datetime precision; (4) the SIP CDR (call detail record) from the VoIP carrier provides a third institutional calendar: major VoIP carriers (Bandwidth.com, Lumen Technologies, AT&T IP Flexible Reach, Comcast Business SIP, Vonage Business Communications, Twilio Elastic SIP Trunking) each generate SIP CDRs recording the originating and terminating numbers, call duration, and SIP response codes — the VoIP carrier's CDR is an independent institutional calendar corroborating the platform's call log; (5) the carrier's STIR/SHAKEN attestation record creates a fourth institutional calendar: under FCC STIR/SHAKEN rules (47 C.F.R. Part 64, Subpart Z), originating carriers must generate a PASSporT (Personal Assertion Token) for each call with an attestation level (A, B, or C) — the PASSporT signing date is on the carrier's own institutional STIR/SHAKEN attestation calendar; a downgraded attestation level suggests the call's origination could not be verified and may indicate spoofed caller ID.
Three initial advisory call types generate untracked billing from the unlawful call date: (1) § 2871 ADAD definition qualification and prior consent analysis advisory — arrives when residential subscriber retains counsel after receiving robocalls (ADAD qualification analysis: [a] confirm that the calling system is an 'automatic dialing-announcing device' under § 2871: the system must incorporate a storage capability of numbers to be called or a random number generator, and when connected to a telephone line, must deliver a prerecorded message; cloud contact center platforms with prerecorded message delivery — including IVR (interactive voice response) systems that answer without a live agent — satisfy the § 2871 definition; [b] confirm the residential telephone subscriber status: § 2872 prohibits ADAD calls to 'residential telephone subscribers' — confirm the subscriber's line is a residential line, not a business line; mobile phones used for residential purposes may qualify; [c] assess the prior consent defense: § 2872 allows ADAD calls if the caller has the prior consent of the person being called — assess whether the defendant can establish that the subscriber actually gave prior consent; consumer consent databases (TrustedForm by ActiveProspect, Jornaya LeadID, AdvancedMD consent records) may show a consent record; [d] assess the established business relationship (EBR) defense: § 2872 also allows ADAD calls to residential subscribers with whom the caller has an 'established business relationship' — an EBR is a prior or existing relationship formed by voluntary two-way communication between the caller and the subscriber; the EBR defense has specific temporal limits under FCC rules: for TCPA purposes, an EBR expires 18 months after a transaction or 3 months after an inquiry; California's EBR under § 2872 has no explicit time limit in the statute; [e] assess the time-of-day violation: § 2872 also prohibits ADAD calls before 9:00 a.m. or after 9:00 p.m. — the call log datetime is the primary evidence of a time-of-day violation; 42–48 min per call); (2) call log evidence and caller identification analysis advisory — arrives when evidence is being gathered (call log analysis: [a] subpoena the telecommunications platform's call log records: a civil subpoena to Twilio/Five9/NICE CXone/Genesys/Avaya/Amazon Connect requests the call detail records for the specific outbound call — the platform's response deadline is on the platform's own compliance calendar; [b] subpoena the VoIP carrier's SIP CDR: the carrier (Bandwidth.com/Lumen/AT&T) can produce the SIP CDR corroborating the platform's call log — the carrier's response deadline is on the carrier's institutional compliance calendar; [c] assess caller ID spoofing: if the caller displayed a spoofed or misleading caller ID (CNAM name or ANI number), the § 2874 caller identification violation provides an additional violation with its own $500 minimum — STIR/SHAKEN attestation records from the originating carrier establish the spoofing; [d] identify the calling entity: reverse-engineering the calling entity from the carrier CDR and the STIR/SHAKEN attestation establishes the defendant's identity — the CNAM registry (Neustar, Iconectiv, TransUnion CNAM) associates the calling telephone number with a registered entity name; [e] assess the wireless carrier's call records: the plaintiff subscriber's wireless carrier (AT&T, Verizon, T-Mobile) may have incoming call records that corroborate the call log — the wireless carrier CDR is on the wireless carrier's institutional billing calendar entirely outside the plaintiff attorney's scheduling control; 42–48 min per call); (3) § 2875 vs. TCPA and CIPA concurrent analysis advisory — arrives before filing (strategic analysis: [a] assess the TCPA § 227(b)(1)(B) concurrent claim: if the call was an automated call or prerecorded message to a residential telephone line without prior express written consent (for telemarketing calls) or prior express consent (for non-telemarketing calls), a concurrent TCPA claim is available — the TCPA provides $500 per violation ($1,500 for willful violations) independently of California § 2875; TCPA § 227 does not itself invoke § 1988(b) (the TCPA is not a § 1983 civil rights statute), so the strict Dague constraint does not apply to TCPA attorney fees; however, TCPA attorney fees are determined under the TCPA's own fee-shifting framework and do not independently provide a Ketchum multiplier; California § 2875 attorney fees are subject to pure Ketchum; Hensley task-level segregation is advisable; [b] assess concurrent CIPA § 637.2 claim: if the robocall used a system that also recorded the recipient's response or background audio — without all-party consent — a concurrent CIPA § 637.2 violation may lie; however, a robocall that simply delivers a prerecorded message without recording the recipient does not violate CIPA; [c] assess the Do Not Call Registry violation: if the call was a telemarketing call to a subscriber registered on the National Do Not Call Registry (47 C.F.R. § 64.1200(c)) or the California Do Not Call Registry (Bus. & Prof. Code § 17590 et seq.), concurrent federal and state DNC violations provide additional claims; [d] assess class action potential: ADAD violations typically affect hundreds or thousands of residential subscribers on the same dialer campaign — the class is ascertainable from the telecommunications platform's own campaign call log records; 42–48 min per call). At 55% untracked: 7 clients × 2 calls × 42 min × 55% = 323.4 min / 60 = 5.39 hours = $1,617–$2,695/year at $300–$500/hr.
Telecommunications platform call log calendar and CPUC complaint calendar and FCC TCPA enforcement calendar: calls on three institutional calendars entirely outside attorney control
A California Pub. Util. Code § 2875 ADAD automated calling case involves three concurrent external institutional calendars entirely outside the plaintiff attorney's scheduling control: the telecommunications platform's own outbound call log calendar [Twilio Programmable Voice, Five9 CRM Dialer, NICE CXone ACD, Genesys Cloud CX, Avaya OneCloud CCaaS, Amazon Connect, Cisco Webex Contact Center, Nuance Conversational AI, LivePerson, and Vonage Contact Center each record: (a) outbound call datetime and time zone (the exact date and time the ADAD system placed the outbound call — on the platform's own institutional call log calendar entirely outside plaintiff attorney's scheduling control); (b) destination telephone number (the ANI of the residential subscriber who received the unlawful call — on the platform's call log); (c) caller ID presented (the CNAM name and ANI displayed to the recipient — on the platform's call log; if spoofed, the STIR/SHAKEN attestation record on the originating carrier's institutional calendar establishes the spoofing); (d) call duration and disposition (answered, unanswered, voicemail, abandoned — on the platform's call log; abandoned calls are separately logged as § 2875 violations); (e) prerecorded message delivery status (message started, completed, or abandoned — on the platform's call log; a message that was delivered for fewer than 30 seconds may not have satisfied the § 2874 caller identification requirement); (f) dialer campaign metadata (campaign ID, contact list version, call attempt number for this destination number — on the platform's campaign management calendar); (g) VoIP carrier SIP CDR (the originating carrier's SIP CDR records the call on the carrier's institutional CDR calendar independently of the platform's call log)]; the California Public Utilities Commission (CPUC) consumer complaint calendar [(a) CPUC complaint intake date (the date CPUC's Consumer Protection and Enforcement Division received the consumer complaint about the unlawful automated call — on CPUC's own institutional complaint management calendar entirely outside plaintiff attorney's scheduling control); (b) CPUC investigation assignment date (the date CPUC assigned the complaint to a Consumer Affairs Branch analyst — on CPUC's institutional calendar); (c) CPUC Order Instituting Investigation (OII) date (if CPUC's Enforcement Division initiates a formal investigation of the calling entity, the OII issuance date is on CPUC's institutional calendar); (d) CPUC enforcement action filing date (if CPUC files a civil enforcement action for § 2875 violations, the filing date is on CPUC's institutional court calendar); (e) CPUC settlement approval date (if the calling entity settles with CPUC, the settlement approval date is on CPUC's institutional calendar)]; and the Federal Communications Commission (FCC) TCPA enforcement calendar [(a) FCC Enforcement Bureau complaint intake date (the date the FCC received a TCPA complaint about the automated call — on FCC's own institutional complaint management calendar entirely outside plaintiff attorney's scheduling control); (b) FCC Letter of Inquiry (LOI) date (if the FCC sends an LOI to the calling entity requesting information about its dialing practices — the LOI date is on FCC's institutional calendar); (c) FCC Notice of Apparent Liability (NAL) date (if the FCC issues an NAL to the calling entity for TCPA violations, the NAL date is on FCC's institutional calendar); (d) FCC Consent Decree date (if the FCC and the calling entity enter into a consent decree settling TCPA violations, the consent decree effective date is on FCC's institutional calendar); (e) FCC STIR/SHAKEN compliance calendar (FCC's STIR/SHAKEN enforcement dates — including any FCC enforcement action against the originating carrier for failing to attest calls properly — are on FCC's institutional calendar)]. Ketchum v. Moses 24 Cal.4th 1122 (2001). PLCM Group 22 Cal.4th 1084 (2000). Hensley v. Eckerhart 461 U.S. 424 (1983). Missouri v. Jenkins 491 U.S. 274 (1989) fees-on-fees.
Three concurrent external institutional calendar advisory call types generate untracked billing: (1) telecommunications platform call log monitoring advisory — arrives when call log evidence is being gathered and preserved (call log calendar analysis: [a] issue a litigation hold demand to the telecommunications platform and VoIP carrier: call log records in cloud contact center platforms are typically retained for 90 days to 2 years depending on the platform's retention policy — a litigation hold must be issued before the records are purged; [b] subpoena the call log records from the platform and carrier: the platform's (Twilio/Five9/Genesys/NICE CXone) and carrier's (Bandwidth/Lumen/AT&T) subpoena response deadlines are on the respective entities' compliance calendars; [c] analyze the campaign call log for the class period: the date range of the ADAD violations is defined by the platform's campaign start date through the campaign end date or the date the calling entity was notified to cease — the campaign metadata in the platform's call log calendar defines the class period; [d] analyze the STIR/SHAKEN attestation records: the originating carrier's STIR/SHAKEN attestation logs — available through the FCC's STIR/SHAKEN analytics service — record the attestation level for each call; a caller ID spoofing violation under § 2874 is established from the STIR/SHAKEN record; 44–50 min per call); (2) CPUC complaint calendar monitoring advisory — arrives when CPUC administrative timeline affects the civil action strategy (CPUC calendar analysis: [a] monitor the CPUC OII issuance: if CPUC initiates an Order Instituting Investigation, the OII creates an administrative record that may provide evidence supporting the plaintiff's civil action under § 2875; [b] assess concurrent CPUC consent decree: if the calling entity settled with CPUC, the consent decree terms and effective date are on CPUC's institutional calendar — the consent decree may bar future ADAD calls and may create collateral estoppel on the § 2875 liability issue; [c] assess CPUC telecommunications certificate suspension: if CPUC suspended or revoked the calling entity's telecommunications certificate for § 2875 violations, the certificate suspension date is on CPUC's institutional calendar; [d] assess the CPUC enforcement action's impact on the class period: if CPUC's enforcement action established that the calling entity violated § 2875 for a defined period, the CPUC's factual findings define the class period for the plaintiff's class action; 44–50 min per call); (3) FCC TCPA enforcement calendar monitoring advisory — arrives when FCC enforcement affects the individual or class action strategy (FCC calendar analysis: [a] monitor the FCC NAL: if the FCC issued an NAL, the NAL amount (typically $10,000 to $1.9 million per violation, or per day) creates independent evidence of the calling entity's TCPA liability; [b] assess FCC consent decree impact: if the FCC's consent decree requires the calling entity to implement a Do Not Call compliance program with specific calendar obligations (e.g., annual reporting dates on the FCC's institutional calendar), those compliance dates are on the FCC's calendar; [c] assess the FCC's analytics service for robocall volume: the FCC's Robocall Analytics and Mitigation Program maintains call volume data that may support the scope of the ADAD violation for class certification; [d] assess concurrent state AG enforcement: several state attorneys general coordinate with the FCC on robocall enforcement — a concurrent California AG enforcement action against the same calling entity may provide additional evidence and leverage for the § 2875 civil action; 44–50 min per call). At 55% untracked: 6 clients × 3 calls × 44 min × 55% = 435.6 min / 60 = 7.26 hours = $2,178–$3,630/year at $300–$500/hr.
§ 2875 attorney fee petition and Ketchum/Dague analysis: calls on the post-judgment fee petition calendar
Fee recovery for § 2875 California ADAD automated calling violations is through § 2875 itself: 'any person who is injured by a violation of this article may bring a civil action for actual damages or five hundred dollars ($500), whichever is greater, for each violation, together with costs of suit and reasonable attorney's fees.' The § 2875 fee petition requires a Hensley lodestar from the DATE OF UNLAWFUL AUTOMATED CALL through ADAD qualification analysis, call log evidence gathering, CPUC and FCC calendar monitoring, litigation, and fee petition. When concurrent TCPA § 227 claims are alleged, the fee analysis requires Hensley task-level segregation: TCPA attorney fees are awarded under TCPA's own fee-shifting framework, not under the Ketchum multiplier framework; California § 2875 attorney fees are subject to pure Ketchum analysis. Ketchum v. Moses 24 Cal.4th 1122 (2001). PLCM Group 22 Cal.4th 1084 (2000). Hensley 461 U.S. 424 (1983). Missouri v. Jenkins 491 U.S. 274 (1989) fees-on-fees.
Two § 2875 post-judgment advisory call types generate untracked billing: (1) § 2875 damages and fee petition component assembly advisory — arrives at judgment (damages and fee components: [a] § 2875 statutory damages: $500 per violation for each unlawful automated call — for a class action with 10,000 members each receiving one unlawful call, the minimum statutory damages are $5,000,000; [b] TCPA § 227(b)(3) concurrent damages: $500 per violation, trebled to $1,500 for willful violations — the TCPA concurrent claim may provide a higher damages recovery for willful violations; [c] injunctive relief: § 2875 and TCPA both support injunctive relief ordering the calling entity to cease ADAD violations and implement a Do Not Call compliance program; [d] § 2875 attorney fees: the lodestar from the first unlawful call date through all § 2875 work and fee petition, segregated from TCPA attorney fee work using Hensley task-level analysis; [e] Missouri v. Jenkins fees-on-fees: attorney fees for preparing the § 2875 fee petition are themselves recoverable; 44–50 min per call); (2) Ketchum/Dague analysis and California-only § 2875 hours identification advisory — arrives at fee petition (segregation analysis: [a] identify hours spent exclusively on California § 2875 theories: any hours spent analyzing § 2871 ADAD definition elements (storage capability, random number generator, prerecorded message delivery) that have no direct TCPA parallel are California-only § 2875 hours — subject to pure Ketchum analysis; [b] identify hours spent on shared § 2875 and TCPA theories: hours spent on prior consent analysis, time-of-day restrictions, and caller identification requirements that overlap between § 2875 and TCPA are shared hours — proportional allocation between California and federal theories is required; [c] apply five Ketchum multiplier factors to § 2875-only hours: (i) ADAD definition qualification uncertainty: at case inception, whether the calling system was an 'ADAD' under § 2871 (required storage capability AND prerecorded message delivery) rather than a predictive dialer or live-agent dialing system was not determinable without discovery of the platform's technical architecture; (ii) prior consent database scope uncertainty: at case inception, whether the defendant maintained a consent database that might support the prior consent defense (TrustedForm/Jornaya LeadID records) was not determinable; (iii) EBR defense temporal scope uncertainty: at case inception, the duration of the established business relationship defense under § 2872 (no explicit time limit in the statute, unlike TCPA's 18-month EBR rule) was uncertain; (iv) STIR/SHAKEN attestation evidence availability uncertainty: at case inception, whether the originating carrier's STIR/SHAKEN records would support a caller ID spoofing claim was not determinable; (v) class certification ascertainability uncertainty: at case inception, whether the class of affected residential subscribers was ascertainable from the platform's call log records was uncertain; 44–50 min per call). At 55% untracked: 5 clients × 2 calls × 44 min × 55% = 242 min / 60 = 4.03 hours = $1,210–$2,017/year at $300–$500/hr.
How ClaimHour fits California § 2875 ADAD automated calling practice
California Pub. Util. Code § 2875 ADAD automated calling solos billing hourly on § 2875 attorney fee recovery — with § 2871 ADAD definition qualification and prior consent analysis advisory calls arriving when residential subscriber retains counsel after receiving unlawful automated calls (DATE OF UNLAWFUL AUTOMATED CALL = primary Welch anchor; in the TELECOMMUNICATIONS PLATFORM'S OWN OUTBOUND CALL LOG: Twilio/Five9/NICE CXone/Genesys Cloud/Avaya OneCloud/Amazon Connect — call datetime, destination number, caller ID, call duration, message delivery status entirely outside plaintiff attorney's scheduling control; § 2875 $500/violation plus mandatory attorney fees; ONLY page where primary Welch anchor is in a cloud communications platform outbound call log; Ketchum/Dague analysis when TCPA § 227 concurrent; DISTINCT from CIPA § 637.2 [recording; § 2875 covers automated dialing without consent]; DISTINCT from CalECPA § 1546.4 [government surveillance; § 2875 covers commercial telemarketing]), telecommunications platform call log monitoring advisory calls on the platform's own institutional call log calendar entirely outside plaintiff attorney's scheduling control, CPUC complaint calendar monitoring advisory calls on CPUC's own institutional calendar entirely outside plaintiff attorney's scheduling control, FCC TCPA enforcement calendar monitoring advisory calls on FCC's own institutional calendar entirely outside plaintiff attorney's scheduling control, and § 2875 attorney fee petition and Ketchum/Dague analysis advisory calls arriving at judgment — and if your § 2875 Hensley lodestar documentation must satisfy the contemporaneous-record standard with Ketchum/Dague analysis from the DATE OF UNLAWFUL AUTOMATED CALL through call log evidence gathering, CPUC/FCC monitoring, litigation, and fee petition, ClaimHour was built for that gap.